[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190610132546.GE8247@lunn.ch>
Date: Mon, 10 Jun 2019 15:25:46 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: Maxime Ripard <maxime.ripard@...tlin.com>, netdev@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-amlogic@...ts.infradead.org,
linus.walleij@...aro.org, bgolaszewski@...libre.com,
peppe.cavallaro@...com, alexandre.torgue@...com,
joabreu@...opsys.com, devicetree@...r.kernel.org,
Neil Armstrong <narmstrong@...libre.com>, khilman@...libre.com,
linux-kernel@...r.kernel.org, davem@...emloft.net,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC next v1 0/5] stmmac: honor the GPIO flags for the PHY reset
GPIO
> if anyone else (just like me) doesn't know about it, there are generic
> bindings defined here: [0]
>
> I just tested this on my X96 Max by defining the following properties
> inside the PHY node:
> reset-delay-us = <10000>;
> reset-assert-us = <10000>;
> reset-deassert-us = <10000>;
> reset-gpios = <&gpio GPIOZ_15 (GPIO_ACTIVE_LOW | GPIO_OPEN_DRAIN)>;
>
> that means I don't need any stmmac patches which seems nice.
> instead I can submit a patch to mark the snps,reset-gpio properties in
> the dt-bindings deprecated (and refer to the generic bindings instead)
> what do you think?
Hi Martin
I know Linus wants to replace all users of old GPIO numbers with gpio
descriptors. So your patches have value, even if you don't need them.
One other things to watch out for. We have generic code at two
levels. Either the GPIO is per PHY, and the properties should be in
the PHY node, or the reset is for all PHYs of an MDIO bus, and then
the properties should be in the MDIO node.
Andrew
Powered by blists - more mailing lists