On 02/06/16 12:14, Rob Herring wrote: > On Sun, May 29, 2016 at 01:12:02PM +0200, Carlo Caione wrote: > > From: Carlo Caione <carlo@xxxxxxxxxxxx> > > > > Add the binding documentation for the Amlogic secure monitor driver. > > > > Signed-off-by: Carlo Caione <carlo@xxxxxxxxxxxx> > > --- > > .../bindings/firmware/meson/meson_sm.txt | 33 ++++++++++++++++++++++ > > 1 file changed, 33 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/firmware/meson/meson_sm.txt > > > > diff --git a/Documentation/devicetree/bindings/firmware/meson/meson_sm.txt b/Documentation/devicetree/bindings/firmware/meson/meson_sm.txt > > new file mode 100644 > > index 0000000..6f0b5bc > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/firmware/meson/meson_sm.txt > > @@ -0,0 +1,33 @@ > > +* Amlogic Secure Monitor > > + > > +In the Amlogic SoCs the Secure Monitor code is used to provide access to the > > +NVMEM, enable JTAG, set USB boot, etc... > > + > > +Required properties for the secure monitor node: > > +- compatible: Should be "amlogic,meson-gxbb-sm" > > + > > +Example: > > + > > + firmware { > > + compatible = "simple-bus"; > > Drop this. Sorry, but no abusing simple-bus to get automagic creation of > your platform device. Sounds reasonable. I can hook this up to some *_initcall. What about introducing a new FIRMWARE_OF_DECLARE() ? Cheers, -- Carlo Caione -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html