On Sat, Dec 10, 2016 at 3:49 AM, Cédric Le Goater <clg@xxxxxxxx> wrote: > This can be used to easily identify a chip on a system with multiple > chips. > > Signed-off-by: Cédric Le Goater <clg@xxxxxxxx> This is very useful when writing userspace that wants to select the mtd device that represents a specific flash chip. Acked-by: Joel Stanley <joel@xxxxxxxxx> > --- > Documentation/devicetree/bindings/mtd/jedec,spi-nor.txt | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mtd/jedec,spi-nor.txt b/Documentation/devicetree/bindings/mtd/jedec,spi-nor.txt > index 2c91c03e7eb0..b7cd02a3ebe8 100644 > --- a/Documentation/devicetree/bindings/mtd/jedec,spi-nor.txt > +++ b/Documentation/devicetree/bindings/mtd/jedec,spi-nor.txt > @@ -65,6 +65,7 @@ Optional properties: > all chips and support for it can not be detected at runtime. > Refer to your chips' datasheet to check if this is supported > by your chip. > +- label : name to assign to mtd. If omitted, the label is the MTD device name. > > Example: > > @@ -75,4 +76,5 @@ Example: > reg = <0>; > spi-max-frequency = <40000000>; > m25p,fast-read; > + label = "System-firmware"; > }; > -- > 2.7.4 > -- 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
