-
Notifications
You must be signed in to change notification settings - Fork 8.3k
boards: nordic: nrf54h20dk: add mbox for event report #100432
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
base: main
Are you sure you want to change the base?
boards: nordic: nrf54h20dk: add mbox for event report #100432
Conversation
cpusec will raise an mbox signal when an event report is generated. This is done when a peripheral triggers an error event to cpusec that cannot be directly passed to cpuapp or cpurad. Define the mbox and enable the IRQ for the corresponding bell in the bellboard. Signed-off-by: Håkon Amundsen <[email protected]>
|
| cpusec_cpurad_event_report: event-report-1-3 { | ||
| compatible = "vnd,mbox-consumer"; | ||
| mboxes = <&cpurad_bellboard 1>; | ||
| mbox-names = "event_channel"; |
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.
event_signal? Not sure about the naming
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.
event should be sufficient
| / { | ||
| ipc { | ||
| cpusec_cpuapp_event_report: event-report-1-2 { | ||
| compatible = "vnd,mbox-consumer"; |
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 think vnd,mbox-consumer was introduced for tests, not boards.
| cpusec_cpuapp_event_report: event-report-1-2 { | ||
| compatible = "vnd,mbox-consumer"; | ||
| mboxes = <&cpuapp_bellboard 1>; | ||
| mbox-names = "event_channel"; |
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.
Have you considered placing this under the cpusec_cpuapp_ipc node? I was imagining we could replace the nordic,ironside-call binding with something that captures all communication with IronSide:
cpusec_cpuapp_ipc: ipc-1-2 {
compatible = "nordic,ironside-ipc";
memory-regions = <&cpusec_cpuapp_ipc_shm>,
<&cpuapp_ironside_se_event_report>;
memory-region-names = "call", "event";
mboxes = <&cpusec_bellboard 12>,
<&cpuapp_bellboard 0>,
<&cpuapp_bellboard 1>;
mbox-names = "call_tx", "call_rx", "event";
};



cpusec will raise an mbox signal when an event report is generated. This is done when a peripheral triggers an error event to cpusec that cannot be directly passed to cpuapp or cpurad.
Define the mbox and enable the IRQ for the corresponding bell in the bellboard.