Skip to content

Conversation

mstasiaknordic
Copy link
Contributor

Requesting/releasing driver device may be ISR safe, but it cannot be reliably known whether managing its power domain is. Is is then assumed that if power domains are used, device is no longer ISR safe. This macro let's us check if we will be requesting/releasing power domains and determines PM device ISR safety value.

Requesting/releasing QDEC device may be ISR safe, but
it cannot be reliably known whether managing its power
domain is. Is is then assumed that if power domains are used,
device is no longer ISR safe. This macro let's us check if
we will be requesting/releasing power domains and determines
PM device ISR safety value.

Upstream PR #: 96402

Signed-off-by: Michał Stasiak <[email protected]>
…fety

Requesting/releasing SPIM device may be ISR safe, but
it cannot be reliably known whether managing its power
domain is. Is is then assumed that if power domains are used,
device is no longer ISR safe. This macro let's us check if
we will be requesting/releasing power domains and determines
PM device ISR safety value.

Upstream PR #: 96402

Signed-off-by: Michał Stasiak <[email protected]>
…fety

Requesting/releasing TWIM device may be ISR safe, but
it cannot be reliably known whether managing its power
domain is. Is is then assumed that if power domains are used,
device is no longer ISR safe. This macro let's us check if
we will be requesting/releasing power domains and determines
PM device ISR safety value.

Upstream PR #: 96402

Signed-off-by: Michał Stasiak <[email protected]>
@nordicjm nordicjm merged commit 5b0d71f into nrfconnect:main Sep 24, 2025
17 checks passed
@mstasiaknordic mstasiaknordic deleted the nrfx_drivers_isr_safe branch October 15, 2025 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants