-
Notifications
You must be signed in to change notification settings - Fork 1.3k
move mramc dtsi to secure dtsi #23240
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
move mramc dtsi to secure dtsi #23240
Conversation
d7c031d
to
0eab341
Compare
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 4b5cf4529f5effc347f83267db1bc13892adb07a more detailssdk-nrf:
Github labels
List of changed files detected by CI (2)
Outputs:ToolchainVersion: 684b32e022 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
0eab341
to
8932b38
Compare
move mram-controller dtsi to secure peripherals as it is secure, bind compaitible of mram node to soc-nv-flash as to differentiate driver from nrf54h20. Signed-off-by: Travis Lam <[email protected]>
8932b38
to
4b5cf45
Compare
move mram-controller dtsi to secure_peripherals.dtsi as it is secure, bind compatible of mram node to soc-nv-flash as to differentiate driver from nrf54h20.