doc: Update direct ISR documentation
Updates the direct ISR documentation to make it more clear that direct ISR handlers should be declared using ISR_DIRECT_DECLARE(). Fixes #85683 Signed-off-by: Peter Mitsis <peter.mitsis@intel.com>
This commit is contained in:
parent
5595de3f68
commit
c9a96477d0
1 changed files with 4 additions and 3 deletions
|
@ -325,9 +325,10 @@ for some low-latency use-cases. Specifically:
|
||||||
potentially make a scheduling decision.
|
potentially make a scheduling decision.
|
||||||
|
|
||||||
Zephyr supports so-called 'direct' interrupts, which are installed via
|
Zephyr supports so-called 'direct' interrupts, which are installed via
|
||||||
:c:macro:`IRQ_DIRECT_CONNECT`. These direct interrupts have some special
|
:c:macro:`IRQ_DIRECT_CONNECT` and whose handlers are declared using
|
||||||
implementation requirements and a reduced feature set; see the definition
|
:c:macro:`ISR_DIRECT_DECLARE`. These direct interrupts have some special
|
||||||
of :c:macro:`IRQ_DIRECT_CONNECT` for details.
|
implementation requirements and a reduced feature set; see the definitions
|
||||||
|
of :c:macro:`IRQ_DIRECT_CONNECT` and :c:macro:`ISR_DIRECT_DECLARE` for details.
|
||||||
|
|
||||||
The following code demonstrates a direct ISR:
|
The following code demonstrates a direct ISR:
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue