-
Notifications
You must be signed in to change notification settings - Fork 729
drivers: serial: uart_nrfx_uarte: Avoid incorrect UARTE disable when using runtime PM #2682
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: uart_nrfx_uarte: Avoid incorrect UARTE disable when using runtime PM #2682
Conversation
Updated manifest to include separate security types for 802.1X in display of scan results when APs have EAP and PMF enabled. BSS display limit based on user-configured non-zero values set via CMD_INIT, along with support for few other regulatory domain updates in firmware. Upstream PR #: 81514 Signed-off-by: Karun Kumar Eagalapati <[email protected]> (cherry picked from commit d5f626e)
EAP_TLS_SHA256 was being identified as EAP_TLS in display scan results. Identify the security type in scan results sent by RPU and display accordingly. Upstream PR #: 81514 Signed-off-by: Ravi Dondaputi <[email protected]> (cherry picked from commit 4092e6d)
fixup! [nrf noup] tree-wide: support NCS Partition Manager (PM) definitions To read the secure memory we need to use soc_secure_mem_read function instead of memcpy. This commit allows to use the soc_secure_mem_read function if the CONFIG_TRUSTED_EXECUTION_NONSECURE and PARTITION_MANAGER is enabled. Signed-off-by: Arkadiusz Balys <[email protected]> (cherry picked from commit 711346a)
fixup! [nrf noup] dfu/boot/mcuboot: fix confirmation in case of USE_PARTITION_MANAGER Fixes this code to correctly check which slot is active, albeit without firmware loader support Signed-off-by: Jamie McCrae <[email protected]> (cherry picked from commit d99f13e)
…05/l10 targets nRF54L05 and nRF54L10 devices that are emulated on nRF54L15 needs to have manually disabled remaining RAM blocks that are outside of their RAM region definitions. Upstream PR #: 82262 Signed-off-by: Nikodem Kastelik <[email protected]> (cherry picked from commit 8798cb4)
…nction Avoid unhandled event calling assert function Signed-off-by: Matthias Hauser <[email protected]> (cherry picked from commit 5438643)
…rt anomaly Add workaround to HFCLK start and stop in nrf54l. In future workaround will be in nrfx driver. Signed-off-by: Krzysztof Chruściński <[email protected]> (cherry picked from commit 2cb2cf2) (cherry picked from commit f57f171)
…using runtime PM When CONFIG_PM_DEVICE_RUNTIME is enabled, the code can incorrectly call nrf_uarte_disable() after TXSTOPPED, even though runtime power management is supposed to handle disabling the UARTE. This happens if the UARTE_FLAG_POLL_OUT flag is not set — in that case, the call to pm_device_runtime_put() is skipped, and nrf_uarte_disable() is called directly instead, which isn't correct when runtime PM is active. This fix prevents nrf_uarte_disable() from being called in this scenario, so that the UARTE is only disabled by the PM system when appropriate. Signed-off-by: Vivek Sahi <[email protected]>
|
none Note: This comment is automatically posted and updated by the Contribs GitHub Action. |
|
The following west manifest projects have changed revision in this Pull Request:
Additional metadata changed:
⛔ DNM label due to: 1 project with metadata changes Note: This message is automatically posted and updated by the Manifest GitHub Action. |
|



When CONFIG_PM_DEVICE_RUNTIME is enabled, the code can incorrectly call
nrf_uarte_disable() after TXSTOPPED, even though runtime power management is
supposed to handle disabling the UARTE.
This happens if the UARTE_FLAG_POLL_OUT flag is not set — in that case,
the call to pm_device_runtime_put() is skipped, and nrf_uarte_disable() is
called directly instead, which isn't correct when runtime PM is active.
This fix prevents nrf_uarte_disable() from being called in this scenario,
so that the UARTE is only disabled by the PM system when appropriate.