Home
last modified time | relevance | path

Searched refs:t (Results 1 – 19 of 19) sorted by relevance

/Kernel-v11.1.0/portable/ThirdParty/GCC/RP2040/include/
Dfreertos_sdk_config.h73 extern void xPortSyncInternalYieldUntilBefore( absolute_time_t t );
74 #define sync_internal_yield_until_before( t ) xPortSyncInternalYieldUntilBefore( t ) argument
/Kernel-v11.1.0/portable/ThirdParty/GCC/Posix/
Dport.c372 struct timespec t; in prvGetTimeNs() local
374 clock_gettime( CLOCK_MONOTONIC, &t ); in prvGetTimeNs()
376 return ( uint64_t ) t.tv_sec * ( uint64_t ) 1000000000UL + ( uint64_t ) t.tv_nsec; in prvGetTimeNs()
/Kernel-v11.1.0/portable/ThirdParty/GCC/RP2040/
Dport.c957 static TickType_t prvGetTicksToWaitBefore( absolute_time_t t ) in prvGetTicksToWaitBefore() argument
959 int64_t xDelay = absolute_time_diff_us( get_absolute_time(), t ); in prvGetTicksToWaitBefore()
1175 void xPortSyncInternalYieldUntilBefore( absolute_time_t t ) in xPortSyncInternalYieldUntilBefore() argument
1177 TickType_t uxTicksToWait = prvGetTicksToWaitBefore( t ); in xPortSyncInternalYieldUntilBefore()
/Kernel-v11.1.0/.github/
DCONTRIBUTING.md20 …/FreeRTOS/FreeRTOS/issues?utf8=%E2%9C%93&q=is%3Aissue) to be sure this hasn't been already reporte…
37 2. You check existing open, and recently merged, pull requests to make sure someone else hasn't add…
Dpull_request_process.md87 3. Don’t mix refactoring, bug fixes and feature development into a single PR. Lets say you are deve…
111 …way - this pull request is going to take a few hours to review and they don’t have a few hours rig…
/Kernel-v11.1.0/portable/GCC/RX600/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/GCC/RX600v2/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/IAR/RX600/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/IAR/RX700v3_DPFPU/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/IAR/RX100/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/Renesas/RX100/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/GCC/RX700v3_DPFPU/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/IAR/RXv2/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/Renesas/RX700v3_DPFPU/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/GCC/RX100/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/Renesas/RX200/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/Renesas/RX600/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/Renesas/RX600v2/
Dreadme.txt56 *4: RX600 ports use MVTIPL instruction but RX610 MCUs don't support this instruction.
/Kernel-v11.1.0/portable/ThirdParty/GCC/ARM_TFM/
DREADME.md64 This macro should be configured as 0 because TF-M doesn't use the secure context management functio…