SourceVu will show references to irq_add_shared_handler() from the following samples and libraries:
Symbols ![]()
loading...
Files ![]()
loading...
irq_add_shared_handler() function
Add a shared interrupt handler for an interrupt on the executing core Use this method to add a handler on an irq number shared between multiple distinct hardware sources (e.g. GPIO, DMA or PIO IRQs). Handlers added by this method will all be called in sequence from highest order_priority to lowest. The irq_set_exclusive_handler() method should be used instead if you know there will or should only ever be one handler for the interrupt. This method will assert if there is an exclusive interrupt handler set for this irq number on this core, or if the (total across all IRQs on both cores) maximum (configurable via PICO_MAX_SHARED_IRQ_HANDLERS) number of shared handlers would be exceeded. \see irq_set_exclusive_handler()
Syntax
Implemented in ![]()
irq.c:356
Arguments
Argument
Description
num
Interrupt number interrupt_nums
handler
The handler to set. See ![]()
irq_handler_t
order_priority
The order priority controls the order that handlers for the same IRQ number on the core are called. The shared irq handlers for an interrupt are all called when an IRQ fires, however the order of the calls is based on the order_priority (higher priorities are called first, identical priorities are called in undefined order). A good rule of thumb is to use PICO_SHARED_IRQ_HANDLER_DEFAULT_ORDER_PRIORITY if you don't much care, as it is in the middle of the priority range by default.
Notes
The order_priority uses \em higher values for higher priorities which is the \em opposite of the CPU interrupt priorities passed to irq_set_priority() which use lower values for higher priorities.