On Wed, Nov 20, 2019 at 03:20:37PM +0100, Khouloud Touil wrote: > NVMEM framework is an interface for the at24 EEPROMs as well as for > other drivers, instead of passing the wp-gpios over the different > drivers each time, it would be better to pass it over the NVMEM > subsystem once and for all. > > Removing the optional property form the device tree binding document. > > Signed-off-by: Khouloud Touil <ktouil@xxxxxxxxxxxx> > --- > Documentation/devicetree/bindings/eeprom/at24.yaml | 6 ------ > 1 file changed, 6 deletions(-) > > diff --git a/Documentation/devicetree/bindings/eeprom/at24.yaml b/Documentation/devicetree/bindings/eeprom/at24.yaml > index e8778560d966..9894237ac432 100644 > --- a/Documentation/devicetree/bindings/eeprom/at24.yaml > +++ b/Documentation/devicetree/bindings/eeprom/at24.yaml > @@ -145,11 +145,6 @@ properties: > over reads to the next slave address. Please consult the manual of > your device. > > - wp-gpios: > - description: > - GPIO to which the write-protect pin of the chip is connected. > - maxItems: 1 > - At least 'wp-gpios: true' is still needed or you need to reference the common definition in nvmem.yaml. The reason being is every possible property (and child node) needs to be listed so we can have errors on any that aren't. Rob
