Home
last modified time | relevance | path

Searched full:group (Results 1 – 25 of 83) sorted by relevance

1234

/Kernel-v11.1.0/include/
Devent_groups.h66 * An event group is a collection of bits to which an application can assign a
67 * meaning. For example, an application may create an event group to convey
74 * bit or a group of specified bits to be active. To continue the CAN bus
84 * to when a bit within an event group is to be cleared, and when bits have to
97 * be used as a parameter to other event group functions.
121 * Create a new event group.
124 * block of memory, in which the event group's structure is stored. If an event
127 * (see https://www.FreeRTOS.org/a00111.html). If an event group is created
129 * provide the memory that will get used by the event group.
130 * xEventGroupCreateStatic() therefore allows an event group to be created
[all …]
/Kernel-v11.1.0/.github/workflows/
Dcoverity_scan.yml29 echo -e "::group::${{ env.bashInfo }} ${{ env.stepName }} ${{ env.bashEnd }}"
43 echo -e "::group::${{ env.bashInfo }} ${{ env.stepName }} ${{ env.bashEnd }}"
58 echo -e "::group::${{ env.bashInfo }} ${{ env.stepName }} ${{ env.bashEnd }}"
77 echo -e "::group::${{ env.bashInfo }} ${{ env.stepName }} ${{ env.bashEnd }}"
97 echo -e "::group::${{ env.bashInfo }} ${{ env.stepName }} ${{ env.bashEnd }}"
116 echo -e "::group::${{ env.bashInfo }} ${{ env.stepName }} ${{ env.bashEnd }}"
Dkernel-demos.yml180 echo -e "::group::${{ env.bashInfo }} ${{ env.stepName }} ${{ env.bashEnd }}"
198 echo -e "::group::${{ env.bashInfo }} ${{ env.stepName }} ${{ env.bashEnd }}"
232 echo -e "::group::${{ env.bashInfo }} ${{ env.stepName }} ${{ env.bashEnd }}"
266 echo -e "::group::${{ env.bashInfo }} ${{ env.stepName }} ${{ env.bashEnd }}"
Dkernel-checks.yml48 echo -e "::group::${{ env.bashInfo }} Install Dependencies ${{ env.bashEnd }}"
57 echo -e "::group::${{ env.bashInfo }} ${{ env.stepName }} ${{ env.bashEnd }}"
/Kernel-v11.1.0/
Devent_groups.c64 …uint8_t ucStaticallyAllocated; /**< Set to pdTRUE if the event group is statically allocated to en…
99 * event group structure. */ in xEventGroupCreateStatic()
105 /* The user has provided a statically allocated event group - use it. */ in xEventGroupCreateStatic()
119 * this event group was created statically in case the event group in xEventGroupCreateStatic()
164 * event group was allocated statically in case the event group is in xEventGroupCreate()
489 /* The value returned is the event group value prior to the bits being in xEventGroupClearBits()
674 /* The event group can only have been allocated dynamically - free in vEventGroupDelete()
680 /* The event group could have been allocated statically or in vEventGroupDelete()
711 /* Check if the event group was statically allocated. */ in xEventGroupGetStaticBuffer()
727 /* Event group must have been statically allocated. */ in xEventGroupGetStaticBuffer()
DMISRA.md99 application at the time of event group creation for data hiding
/Kernel-v11.1.0/portable/ThirdParty/xClang/XCOREAI/
Dportasm.S6 Therfore it must be added to the rtos_isr group with the
8 .weak _fptrgroup.rtos_isr.nstackwords.group
9 .add_to_set _fptrgroup.rtos_isr.nstackwords.group, vTaskSwitchContext.nstackwords, vTaskSwitchConte…
/Kernel-v11.1.0/portable/CCS/ARM_CM3/
Dport.c256 /* Calculate the maximum acceptable priority group value for the number in xPortStartScheduler()
292 /* Shift the priority group value back to its position within the AIRCR in xPortStartScheduler()
687 * assume a non-zero priority group setting, in which cases using a value in vPortValidateInterruptPriority()
/Kernel-v11.1.0/portable/GCC/RX600/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/GCC/RX600v2/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/IAR/RX600/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/IAR/RX700v3_DPFPU/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/IAR/RX100/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/Renesas/RX100/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/GCC/RX700v3_DPFPU/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/IAR/RXv2/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/Renesas/RX700v3_DPFPU/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/GCC/RX100/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/Renesas/RX200/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/Renesas/RX600/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/Renesas/RX600v2/
Dreadme.txt4 RX MCU Group CPU FPU FPU Port Layer
/Kernel-v11.1.0/portable/IAR/ARM_CM7/r0p1/
Dport.c322 /* Calculate the maximum acceptable priority group value for the number in xPortStartScheduler()
358 /* Shift the priority group value back to its position within the AIRCR in xPortStartScheduler()
759 * assume a non-zero priority group setting, in which cases using a value in vPortValidateInterruptPriority()
/Kernel-v11.1.0/portable/IAR/ARM_CM3/
Dport.c296 /* Calculate the maximum acceptable priority group value for the number in xPortStartScheduler()
332 /* Shift the priority group value back to its position within the AIRCR in xPortStartScheduler()
727 * assume a non-zero priority group setting, in which cases using a value in vPortValidateInterruptPriority()
/Kernel-v11.1.0/portable/CCS/ARM_CM4F/
Dport.c275 /* Calculate the maximum acceptable priority group value for the number in xPortStartScheduler()
311 /* Shift the priority group value back to its position within the AIRCR in xPortStartScheduler()
712 * assume a non-zero priority group setting, in which cases using a value in vPortValidateInterruptPriority()
/Kernel-v11.1.0/portable/GCC/ARM_AARCH64_SRE/
DportASM.S272 * GIC documentation [1], Group 0 interrupts are always signaled as FIQs. Since
273 * this handler is only for IRQs, We can safely assume Group 1 while accessing

1234