On 17 January 2017 at 12:03, Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx> wrote: > The MR25 family doesn't support JEDEC, so they need explicit mentioning > in the list of supported spi IDs. This makes it possible to add these > using for example: > > compatible = "everspin,mr25h40"; (...) > diff --git a/Documentation/devicetree/bindings/mtd/jedec,spi-nor.txt b/Documentation/devicetree/bindings/mtd/jedec,spi-nor.txt > index 2c91c03e7eb0..3e920ec5c4d3 100644 > --- a/Documentation/devicetree/bindings/mtd/jedec,spi-nor.txt > +++ b/Documentation/devicetree/bindings/mtd/jedec,spi-nor.txt > @@ -14,6 +14,8 @@ Required properties: > at25df641 > at26df081a > mr25h256 > + mr25h10 > + mr25h40 > mx25l4005a > mx25l1606e > mx25l6405d Uh, this is getting a never-ending-story... If these chipsets don't support JEDEC, should we keep them in jedec,spi-nor.txt? -- Rafał -- 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
