Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Real time embedded FreeRTOS mailing list 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT Training




Loading

Chaining the higherPriorityTaskWoken variable

Posted by Paul Coleman on March 14, 2012
I have a situation where I'm responding to a number of GPIO interrupts with one ISR and I just want to clarify that I'm using the correct method of dealing with the situation whereby a higher priority task will be woken as a result of this interrupt.

Looking at the source code for xSemaphoreGiveFromISR() it looks as though it's okay to chain the use of the variable higherPriorityTaskWoken as shown below as opposed to creating separate variables for each call to xSemaphoreGiveFromISR and then bitwise oring them together to create the final return value which is passed into the portEND_SWITCHING_ISR macro e.g.

ISR {
portBASE_TYPE higherPriorityTaskWoken = pdFALSE; // only set its initial value once

if(some event)
xSemaphoreGiveFromISR(semA, &higherPriorityTaskWoken); // using the variable here

if(some other event)
xSemaphoreGiveFromISR(semB, &higherPriorityTaskWoken); // and the same one here again

if(some other event)
xSemaphoreGiveFromISR(semC, &higherPriorityTaskWoken); // and here again

portEND_SWITCHING_ISR(higherPriorityTaskWoken);
}

I would be grateful if somebody could just clarify that the above is correct.

Many thanks, Paul.

RE: Chaining the higherPriorityTaskWoken variable

Posted by Richard on March 14, 2012
Yes your code is fine.

[I caused a bit of confusion on this maybe in my reply to a recent post]

Regards.

RE: Chaining the higherPriorityTaskWoken variable

Posted by Paul Coleman on March 14, 2012
Okay thanks for the clarification, it makes the code a lot cleaner than having separate variables and I'm all for that :)

Regards, Paul.


[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]




Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.

Latest News:

FreeRTOS V9.0.0 is now available for download.


Free TCP/IP and file system demos for the RTOS


Sponsored Links

⇓ Now With No Code Size Limit! ⇓
⇑ Free Download Without Registering ⇑


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Renesas Electronics Gold Alliance RTOS Partner.jpg

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Atmel RTOS partner supporting ARM Cortex-M3 and AVR32 microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Xilinx Microblaze and Zynq partner

Silicon Labs low power RTOS partner

Altera RTOS partner for Nios II and Cortex-A9 SoC

Freescale Alliance RTOS Member supporting ARM and ColdFire microcontrollers

Infineon ARM Cortex-M microcontrollers

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

Cypress RTOS partner supporting ARM Cortex-M3

Fujitsu RTOS partner supporting ARM Cortex-M3 and FM3

Microsemi (previously Actel) RTOS partner supporting ARM Cortex-M3

Atollic Partner

IAR Partner

Keil ARM Partner

Embedded Artists