On Tue, Oct 24, 2023 at 05:58:06PM -0300, Luiz Angelo Daros de Luca wrote: > Realtek switches can now be reset using a reset controller. > > The 'reset-gpios' were never mandatory for the driver, although they > are required for some devices if the switch reset was left asserted by > a previous driver, such as the bootloader. > > Signed-off-by: Luiz Angelo Daros de Luca <luizluca@xxxxxxxxx> > Cc: devicetree@xxxxxxxxxxxxxxx > --- I believe there was a rule that device tree binding patches should come before the user of those bindings. > Documentation/devicetree/bindings/net/dsa/realtek.yaml | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/net/dsa/realtek.yaml b/Documentation/devicetree/bindings/net/dsa/realtek.yaml > index cce692f57b08..070821eae2a7 100644 > --- a/Documentation/devicetree/bindings/net/dsa/realtek.yaml > +++ b/Documentation/devicetree/bindings/net/dsa/realtek.yaml > @@ -59,6 +59,12 @@ properties: > description: GPIO to be used to reset the whole device > maxItems: 1 > > + resets: > + maxItems: 1 > + > + reset-names: > + const: switch > + > realtek,disable-leds: > type: boolean > description: | > @@ -127,7 +133,6 @@ else: > - mdc-gpios > - mdio-gpios > - mdio > - - reset-gpios Ideally, the change that makes the reset-gpios optional should not be named "add reset controller", unless it is actually the addition of the reset controller which makes it optional. Which you say is not the case. So, I think it should be a separate change. > > required: > - compatible > -- > 2.42.0 > I also commented this on the other change: please move the example here.
