hujun260 commented on code in PR #18322: URL: https://github.com/apache/nuttx/pull/18322#discussion_r2757141404
########## sched/semaphore/sem_post.c: ########## @@ -37,57 +37,15 @@ #include "semaphore/semaphore.h" /**************************************************************************** - * Public Functions - ****************************************************************************/ - -/**************************************************************************** - * Name: nxsem_post_slow - * - * Description: - * When a kernel thread has finished with a semaphore, it will call - * nxsem_post(). This function unlocks the semaphore referenced by sem - * by performing the semaphore unlock operation on that semaphore. - * - * If the semaphore value resulting from this operation is positive, then - * no tasks were blocked waiting for the semaphore to become unlocked; the - * semaphore is simply incremented. - * - * If the value of the semaphore resulting from this operation is zero, - * then one of the tasks blocked waiting for the semaphore shall be - * allowed to return successfully from its call to nxsem_wait(). - * - * Input Parameters: - * sem - Semaphore descriptor - * - * Returned Value: - * This is an internal OS interface and should not be used by applications. - * It follows the NuttX internal error return policy: Zero (OK) is - * returned on success. A negated errno value is returned on failure. - * - * Assumptions: - * This function may be called from an interrupt handler. - * + * Private Functions ****************************************************************************/ -int nxsem_post_slow(FAR sem_t *sem) +static inline_function +int get_blocking(FAR sem_t *sem, bool mutex, bool *blocking) Review Comment: Although ASIL D does not mandate a specific requirement for CCM, certification bodies often set a limit of less than 20 based on industry best practices or conventions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
