mirror of
https://github.com/espressif/esp-nimble.git
synced 2026-10-16 10:37:22 +00:00
Andrzej Kaczmarek
f1dba08467
This patch adds port of Nimble stack to FreeRTOS based on nRF5 SDK. It's split into 'common' part which can be used a base for porting to any other platform and 'freertos_nrf5_sdk' which has FreeRTOS-specific files and makefile. Building and flashing is similar to other demo apps from nRF5 SDK: $ make -C porting/freertos_nrf5_sdk The resulting image can be flashed on nRF52 DK: $ make -C porting/freertos_nrf5_sdk flash Location of nRF5 SDK is set by NRF5_SDK_ROOT variable. By default it is set to 'nrf5_sdk' subdirectory so a symlink would work just fine: $ ln -s <x>/nRF5_SDK_12.3.0_d7731ad porting/freertos_nrf5_sdk/nrf5_sdk
68 lines
2.0 KiB
C
68 lines
2.0 KiB
C
/*
|
|
* Licensed to the Apache Software Foundation (ASF) under one
|
|
* or more contributor license agreements. See the NOTICE file
|
|
* distributed with this work for additional information
|
|
* regarding copyright ownership. The ASF licenses this file
|
|
* to you under the Apache License, Version 2.0 (the
|
|
* "License"); you may not use this file except in compliance
|
|
* with the License. You may obtain a copy of the License at
|
|
*
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
*
|
|
* Unless required by applicable law or agreed to in writing,
|
|
* software distributed under the License is distributed on an
|
|
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
* KIND, either express or implied. See the License for the
|
|
* specific language governing permissions and limitations
|
|
* under the License.
|
|
*/
|
|
|
|
#ifndef _OS_MUTEX_H_
|
|
#define _OS_MUTEX_H_
|
|
|
|
#include "os/os.h"
|
|
#include "os/queue.h"
|
|
|
|
#ifdef __cplusplus
|
|
extern "C" {
|
|
#endif
|
|
|
|
struct os_mutex
|
|
{
|
|
SLIST_HEAD(, os_task) mu_head; /* chain of waiting tasks */
|
|
uint8_t _pad;
|
|
uint8_t mu_prio; /* owner's default priority*/
|
|
uint16_t mu_level; /* call nesting level */
|
|
struct os_task *mu_owner; /* owners task */
|
|
};
|
|
|
|
/*
|
|
XXX: NOTES
|
|
-> Should we add a magic number or flag to the mutex structure so
|
|
that we know that this is a mutex? We can use it for double checking
|
|
that a proper mutex was passed in to the API.
|
|
-> What debug information should we add to this structure? Who last
|
|
acquired the mutex? File/line where it was released?
|
|
-> Should we add a name to the mutex?
|
|
-> Should we add a "os_mutex_inspect() api?
|
|
*/
|
|
|
|
/* XXX: api to create
|
|
os_mutex_inspect();
|
|
*/
|
|
|
|
/* Initialize a mutex */
|
|
os_error_t os_mutex_init(struct os_mutex *mu);
|
|
|
|
/* Release a mutex */
|
|
os_error_t os_mutex_release(struct os_mutex *mu);
|
|
|
|
/* Pend (wait) for a mutex */
|
|
os_error_t os_mutex_pend(struct os_mutex *mu, uint32_t timeout);
|
|
|
|
#ifdef __cplusplus
|
|
}
|
|
#endif
|
|
|
|
#endif /* _OS_MUTEX_H_ */
|