On Tue, Mar 9, 2021 at 2:59 PM Michael Walle <michael@xxxxxxxx> wrote: > > Hi Tim, > > Am 2021-03-09 23:00, schrieb Tim Harvey: > > Document the compatible value for the Fujitsu MB85RS4MT SPI > > FRAM EEPROM device so that it can be used in DTS files. > > > > This is a 512KiB FRAM EEPROM. > > > > Signed-off-by: Tim Harvey <tharvey@xxxxxxxxxxxxx> > > --- > > Documentation/devicetree/bindings/eeprom/at25.yaml | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/Documentation/devicetree/bindings/eeprom/at25.yaml > > b/Documentation/devicetree/bindings/eeprom/at25.yaml > > index 6a2dc8b3ed14..f594db72b711 100644 > > --- a/Documentation/devicetree/bindings/eeprom/at25.yaml > > +++ b/Documentation/devicetree/bindings/eeprom/at25.yaml > > @@ -26,6 +26,7 @@ properties: > > - anvo,anv32e61w > > - atmel,at25256B > > - fujitsu,mb85rs1mt > > + - fujitsu,mb85rs4mt > > - fujitsu,mb85rs64 > > - microchip,at25160bn > > - microchip,25lc040 > > Hm, the driver is spi-nor but this is for the at25 driver. Is > this correct? Doesn't it work if you just add the ID to > spi-nor/fujitsu.c and use 'compatible = "jedec,spi-nor' ? > Michael, Yes it works just fine as 'compatible = "jedec,spi-nor"' and that makes sense. I'll drop this patch and update my device-tree accordingly. Thanks, Tim
