[nrf fromlist] drivers: nrfx: enable cross domain pins for nRF54L15 #2902
Conversation
This file contains hidden or 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
mstasiaknordic
force-pushed
the
nrf54l15_cross_domain_pins
branch
from
2367850 to
6d04536
Compare
mstasiaknordic
changed the title
mstasiaknordic
force-pushed
the
nrf54l15_cross_domain_pins
branch
from
6d04536 to
ff502ff
Compare
|
mstasiaknordic
force-pushed
the
nrf54l15_cross_domain_pins
branch
from
ff502ff to
f501516
Compare
mstasiaknordic
force-pushed
the
nrf54l15_cross_domain_pins
branch
from
f501516 to
e3bb011
Compare
mstasiaknordic
commented
Jul 16, 2025
...drivers/spi/spi_controller_peripheral/boards/nrf54l15dk_nrf54l15_cpuapp_cross_domain.overlay
Show resolved
Hide resolved
mstasiaknordic
commented
Jul 16, 2025
tests/drivers/uart/uart_elementary/boards/nrf54l15dk_nrf54l15_cpuapp_cross_domain.overlay
Show resolved
Hide resolved
nordic-segl
reviewed
Jul 16, 2025
mstasiaknordic
force-pushed
the
nrf54l15_cross_domain_pins
branch
from
e3bb011 to
b9a228f
Compare
mstasiaknordic
commented
Jul 17, 2025
Comment on lines
+110
to
+108
| harness_config: | ||
| fixture: spi_p1_p2_loopback |
Contributor
Author
There was a problem hiding this comment.
Added spi_p1_p2_loopback fixture
mstasiaknordic
commented
Jul 17, 2025
Comment on lines
+118
to
+103
| harness_config: | ||
| fixture: uart_p1_p2_loopback |
Contributor
Author
There was a problem hiding this comment.
Added uart_p1_p2_loopbkac fixture, unfortunately, SPI and UART cases require conflicting setups, so two separate fixtures had to be added
nordic-segl
approved these changes
Jul 17, 2025
nordic-segl
requested review from
kl-cruz,
nika-nordic,
nordic-babu,
nordic-bami,
nordic-krch,
nordic-pikr and
nordic-piks
nordic-pikr
approved these changes
Jul 17, 2025
mstasiaknordic
force-pushed
the
nrf54l15_cross_domain_pins
branch
from
b9a228f to
31fa263
Compare
kl-cruz
approved these changes
Jul 18, 2025
mstasiaknordic
force-pushed
the
nrf54l15_cross_domain_pins
branch
2 times, most recently
from
1f48dec to
b1e50da
Compare
…for nRF54L15 UARTE20 and UARTE21 instances enable usage of pins on different port, but require request for constant latency mode. Added handling of such scenario in the driver. Added testcase to cover it. Upstream PR #: 90197 Signed-off-by: Michał Stasiak <[email protected]>
…for nRF54L15 SPI(M/S)20 and SPIM(M/S)21 instances enable usage of pins on different port, but require request for constant latency mode. Added handling of such scenario in the driver. Added testcase to cover it. Upstream PR #: 90197 Signed-off-by: Michał Stasiak <[email protected]>
mstasiaknordic
force-pushed
the
nrf54l15_cross_domain_pins
branch
from
b1e50da to
fb1683a
Compare
masz-nordic
approved these changes
Jul 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
UARTE20, UARTE21, SPI(M/S)20 and SPIM(M/S)21 instances enable usage of pins on different port, but require request for constant latency mode. Added handling of such scenario in the driver. Added testcases to cover it.