-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drivers: serial: nrfx_uarte: Add requesting of HSFLL GD clock when fast UARTE (uart120) is used #82103
Conversation
Looks correct :) |
42b2610
to
d634eee
Compare
0210d32
to
6979d1a
Compare
6979d1a
to
83b4112
Compare
/* Macro must resolve to literal 0 or 1 */ | ||
#define INSTANCE_IS_FAST(unused, prefix, idx, _) \ | ||
COND_CODE_1(DT_NODE_HAS_STATUS_OKAY(UARTE(idx)), \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should stay so that it does not take disabled instances into account
83b4112
to
5e192c1
Compare
e234a23
e234a23
to
60277e0
Compare
Merged as part of nrfconnect/sdk-zephyr#2385 |
Reopening as the commits still need to be merged upstream. In the above PR, they were only cherry-picked into the downstream fork. |
Rebased. |
ah my bad :) I did not notice this one was upstream :) |
is the DNM intentional? |
f8f9ed7
to
051140b
Compare
Add clock source for timer120 and timer121 nodes Signed-off-by: Krzysztof Chruściński <[email protected]>
Add requesting for global HFSLL when fast instance TIMER (e.g. TIMER120 in nrf54h20) is used. Signed-off-by: Krzysztof Chruściński <[email protected]>
Request fast global domain to run at 320 MHz during fast UARTE activity. As request is asynchronous it cannot be called from an ISR. Due to complexity to handle that without device runtime power management a requirement is added so that if fast UARTE is used device runtime PM must be enabled. Clock is request and released in PM resume and suspended actions which in case of fast UARTE are only called from thread context. Signed-off-by: Krzysztof Chruściński <[email protected]>
Enable device runtime PM for nrf54h20dk/nrf54h20/cpuapp where fast UARTE (uart120) is tested. Signed-off-by: Krzysztof Chruściński <[email protected]>
Added clock request and release in resume and suspend actions. It is required for the fast UARTE peripheral (uart120 in nrf54h20). Since it would be tricky to handle that outside of PM actions added build time check which enforces use of device runtime PM when fast UARTE is used (device power PM is de facto a must in nrf54h20 so it is not a real limitation).
Due to device runtime PM requirement,
uart_async_api
test configuration for nrf54h20dk/nrf54h20/cpuapp has been extended to enable PM.Work from PR #81527 had to be included.DNM until #81735.