On Mon, Nov 30, 2015 at 04:21:52PM +0000, Paul Burton wrote: > Add documentation for the simple img,boston devicetree binding & the > boot protocol used to pass the devicetree to the kernel. > > Signed-off-by: Paul Burton <[email protected]> > --- > > Documentation/devicetree/bindings/mips/img/boston.txt | 15 +++++++++++++++ > MAINTAINERS | 5 +++++ > 2 files changed, 20 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mips/img/boston.txt > > diff --git a/Documentation/devicetree/bindings/mips/img/boston.txt > b/Documentation/devicetree/bindings/mips/img/boston.txt > new file mode 100644 > index 0000000..27b2806 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mips/img/boston.txt > @@ -0,0 +1,15 @@ > +Imagination Technologies Boston Development Board > +================================================= > + > +Required properties: > +-------------------- > + - compatible: Must be "img,boston".
No SOC compatible in addition? > + > +Boot protocol: > +-------------- > +In accordance with the MIPS UHI specification[1], the bootloader must pass > the > +following arguments to the kernel: > + - $a0: -2. > + - $a1: KSEG0 address of the flattened device-tree blob. If this is standard, I don't know that we need to repeat it for every board. Rob > + > +[1] http://prplfoundation.org/wiki/MIPS_documentation -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
