Re: [PATCH v5] dt-bindings: arm: keystone: add boot_* mboxes to ti,sci

[Nishanth Menon <nm@ti.com>]

On 06:57-20251217, Rob Herring wrote:
> > >    - |
> > >      dmsc: system-controller@44083000 {
> > > -      compatible = "ti,k2g-sci";
> > > +      compatible = "ti,am654-sci";
> > >        ti,host-id = <12>;
> > > -      mbox-names = "rx", "tx";
> > > -      mboxes = <&secure_proxy_main 11>,
> > > -               <&secure_proxy_main 13>;
> > > +      mbox-names = "rx", "tx", "notify", "boot_rx", "boot_tx";
> > > +      mboxes= <&secure_proxy_mcu 6>, <&secure_proxy_mcu 8>,
> > > +        <&secure_proxy_mcu 5>, <&secure_proxy_mcu 5>, <&secure_proxy_mcu 4>;
> > >        reg-names = "debug_messages";
> > >        reg = <0x44083000 0x1000>;
> > 
> > Please add a different example for am654, i want to make sure k2g still
> > continues to be checked.
> > 
> > That said, AM62 series of devices do not use notification pipe for
> > standard communication. So, the schema will break for those.
> > 
> > in summary:
> > k2g: rx, tx
> > am654, j721e, j721s2, j7200, j784s4, .. : rx, tx, notify, boot_rx,
> > boot_tx, boot_notify
> > am625, am62p ..: rx, tx, boot_rx, boot_tx, boot_notify
> > 
> > we will need three examples, and will need to add am62x series as one
> > additional compatible.
> 
> Do we really? We have a whole tree of examples in .dts files.

We do not. But, I would rather leave existing valid example as is rather
than modifying it for a new compatible that was just added.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource