Whoops, wrong patch, please ignore this v2. > mtd: st_spi_fsm: Provide documentation for boot device mask property > > The system configuration registers which display which device the system > booted on are in the same place on all boards which support the FSM. > However, the bits do shift every so slightly. To combat these we're > adding a new property which supplies the necessary mask used to abstract > the required information. > > Cc: [email protected] > Signed-off-by: Lee Jones <[email protected]> > > diff --git a/Documentation/devicetree/bindings/mtd/st-fsm.txt > b/Documentation/devicetree/bindings/mtd/st-fsm.txt > index c248939..2ef9710 100644 > --- a/Documentation/devicetree/bindings/mtd/st-fsm.txt > +++ b/Documentation/devicetree/bindings/mtd/st-fsm.txt > @@ -11,6 +11,10 @@ Optional properties: > - st,syscfg : Phandle to boot-device system configuration > registers > - st,boot-device-reg : Address of the aforementioned boot-device > register(s) > - st,boot-device-spi : Expected boot-device value if booted via this device > + - st,boot-device-msk : Mask to use when extracting boot device from the > + above system config registers > + NB: If any of the st,boot-device-* properties are missing, the driver falls > + back to the default assumption of 'booted from SPI'. > > Example: > spifsm: spifsm@fe902000{
-- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- 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/
