On Tue, Oct 10, 2023 at 09:09:25PM +0200, Marek Vasut wrote: > The ST M24C32-D behaves as a regular M24C32, except for the -D variant > which uses up another I2C address for Additional Write lockable page. > This page is 32 Bytes long and can contain additional data. Document > compatible string for it, so users can describe that page in DT. Note > that users still have to describe the main M24C32 area separately as > that is on separate I2C address from this page. So 2 nodes for 1 device? Wouldn't it make more sense for the 1 node to have 2 addresses? > > Signed-off-by: Marek Vasut <marex@xxxxxxx> > --- > Cc: Arnd Bergmann <arnd@xxxxxxxx> > Cc: Bartosz Golaszewski <brgl@xxxxxxxx> > Cc: Conor Dooley <conor+dt@xxxxxxxxxx> > Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@xxxxxxxxxx> > Cc: Rob Herring <robh+dt@xxxxxxxxxx> > Cc: devicetree@xxxxxxxxxxxxxxx > Cc: linux-i2c@xxxxxxxxxxxxxxx > --- > Documentation/devicetree/bindings/eeprom/at24.yaml | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/devicetree/bindings/eeprom/at24.yaml b/Documentation/devicetree/bindings/eeprom/at24.yaml > index 98139489d4b5c..7be127e9b2507 100644 > --- a/Documentation/devicetree/bindings/eeprom/at24.yaml > +++ b/Documentation/devicetree/bindings/eeprom/at24.yaml > @@ -67,6 +67,8 @@ properties: > pattern: cs16$ > - items: > pattern: c32$ > + - items: > + pattern: c32d-wl$ > - items: > pattern: cs32$ > - items: > -- > 2.40.1 >
