nRF clock_control add ZLI API #2386
Merged
+121
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ppryga-nordic
force-pushed
the
nrf-clock-control-zli-api-dowstream
branch
from
3409331 to
d140127
Compare
bjarki-andreasen
approved these changes
Dec 16, 2024
masz-nordic
approved these changes
Dec 16, 2024
kl-cruz
approved these changes
Dec 16, 2024
ppryga-nordic
force-pushed
the
nrf-clock-control-zli-api-dowstream
branch
from
d140127 to
dfd1b3d
Compare
|
Can you close the auto manifest PR if it is not needed and open PRs with the manifest PR skip line if they are not needed? |
ppryga-nordic
force-pushed
the
nrf-clock-control-zli-api-dowstream
branch
from
dfd1b3d to
f397649
Compare
… APIs Add zero latency interrupt safe APIs to allow requesting and releasing HFXO. These will be used from components running in zero latency interrupt context, like the bluetooth stack. Co-authored-by: Piotr Pryga <[email protected]> Signed-off-by: Bjarki Arge Andreasen <[email protected]> Signed-off-by: Piotr Pryga <[email protected]> (cherry picked from commit 2aec438) Signed-off-by: Piotr Pryga <[email protected]>
…sr API Implement the zero latency interrupt safe APIs to the HFXO clock commonly used by the bluetooth stach from zero latency interrupt context. Co-authored-by: Piotr Pryga <[email protected]> Signed-off-by: Bjarki Arge Andreasen <[email protected]> Signed-off-by: Piotr Pryga <[email protected]> (cherry picked from commit 73a45a7) Signed-off-by: Piotr Pryga <[email protected]>
ppryga-nordic
force-pushed
the
nrf-clock-control-zli-api-dowstream
branch
2 times, most recently
from
0687e98 to
c5923e4
Compare
|
|
There were redundant code in full_irq_lock(), full_irq_unlock() functions that supposed to be used when ZLI IRQs are disabled. These functions are compiled in only when CONFIG_ZERO_LATENCY_IRQS is set, hence the non-ZLI execution path was never included in final binaries. Signed-off-by: Piotr Pryga <[email protected]> (cherry picked from commit 233095c3f452c05683f0410140e737d89567d927) Signed-off-by: Piotr Pryga <[email protected]>
ppryga-nordic
force-pushed
the
nrf-clock-control-zli-api-dowstream
branch
from
c5923e4 to
0862348
Compare
|
@carlescufi done, should I re-run manifest PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement the zero latency interrupt safe APIs to the HFXO clock commonly used by the Bluetooth stack from zero latency interrupt context.
The PR brings changes done in upstream (+ one cleanup change that is in a PR).