On Mon, Jun 10, 2024 at 11:39:49AM +0300, Viacheslav Bocharov wrote: > Add secure-monitor property to schema for meson-gx-socinfo-sm driver. "bindings are for hardware, not drivers". Why purpose does the "secure monitor" serve that the secure firmware needs a reference to it? Thanks, Conor. > > Signed-off-by: Viacheslav Bocharov <adeep@xxxxxxxxx> > --- > .../bindings/arm/amlogic/amlogic,meson-gx-ao-secure.yaml | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/arm/amlogic/amlogic,meson-gx-ao-secure.yaml b/Documentation/devicetree/bindings/arm/amlogic/amlogic,meson-gx-ao-secure.yaml > index 7dff32f373cb..1128a794ec89 100644 > --- a/Documentation/devicetree/bindings/arm/amlogic/amlogic,meson-gx-ao-secure.yaml > +++ b/Documentation/devicetree/bindings/arm/amlogic/amlogic,meson-gx-ao-secure.yaml > @@ -32,6 +32,10 @@ properties: > reg: > maxItems: 1 > > + secure-monitor: Missing a vendor prefix. > + description: phandle to the secure-monitor node > + $ref: /schemas/types.yaml#/definitions/phandle > + > amlogic,has-chip-id: > description: | > A firmware register encodes the SoC type, package and revision > -- > 2.45.2 >
Attachment:
signature.asc
Description: PGP signature
