Re: [PATCH v3 1/3] dt-bindings: remoteproc: k3-m4f: Add bindings for K3 AM64x SoCs

[Hari Nagalla]

On 3/8/23 14:58, Mathieu Poirier wrote:
> > +required:
> > +  - compatible
> > +  - reg
> > +  - reg-names
> > +  - ti,sci
> > +  - ti,sci-dev-id
> > +  - ti,sci-proc-ids
> > +  - resets
> > +  - firmware-name
> > +  - mboxes
> The 'mboxes' property is marked as required but the description section above
> clearly state the M4F can operate without IPC.
Well, when the M4F is used as a safety processor it is typically booted 
from SBL/u-boot and may isolate the MCU domain from main domain/A53 to 
function in higher safety level. In these scenarios there is no remote 
proc handling of M4F life cycle management (LCM) and IPC. But, on the 
other hand, when the M4F is used as a non safety processor its LCM is 
handled by remote proc(main domain) and mailboxes for IPC are required.