-
Notifications
You must be signed in to change notification settings - Fork 1.4k
manifest: Update sdk-zephyr revision #22732
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
Conversation
The following west manifest projects have changed revision in this Pull Request: ✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 80d256ceb74346862ab65b151dc9432b9a6d02d6 more detailssdk-nrf:
nrfxlib:
zephyr:
Github labels
List of changed files detected by CI (60)
Outputs:ToolchainVersion: 4aa3467a6d Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
You can find the documentation preview for this PR here. |
06d6e32
to
6cadd90
Compare
29df69e
to
e4faaa6
Compare
The clock latency configuration for both nrf-802154 and MPSL is now done in DTS. Signed-off-by: Rafał Kuźnia <[email protected]>
The node label hfxo is assumed to be a 32 MHz oscillator on previous SoC families. To avoid inconsistency, the 64 MHz hfxo node was renamed to hfxo64m. Signed-off-by: Rafał Kuźnia <[email protected]>
e4faaa6
to
80d256c
Compare
@nrfconnect/ncs-co-drivers @nrfconnect/ncs-co-build-system PTAL |
int "HFCLK ramp-up latency in microsecond, assumed by MPSL to wait for the clock availability" | ||
default 1650 if SOC_SERIES_NRF54LX | ||
default $(dt_node_int_prop_int,/clocks/hfxo,startup-time-us) if $(dt_node_has_prop,/clocks/hfxo,startup-time-us) | ||
default $(dt_node_int_prop_int,/oscillators/hfxo,startup-time-us) if $(dt_node_has_prop,/oscillators/hfxo,startup-time-us) |
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.
Why not use the hfxo
node label, actually? I mean:
default $(dt_nodelabel_int_prop,hfxo,startup-time-us) if $(dt_nodelabel_has_prop,hfxo,startup-time-us)
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.
I didn't know that this existed. Could it be done in subsequent PR to unblock manifest updates for others?
The clock latency configuration for both nrf-802154 and MPSL is now done in DTS.