From: Bernhard Walle <hidden> Date: 2016-02-08 20:27:43
We need that for a custom hardware that needs the reverse reset
sequence.
Signed-off-by: Bernhard Walle <redacted>
---
Documentation/devicetree/bindings/net/fsl-fec.txt | 3 +++
drivers/net/ethernet/freescale/fec_main.c | 8 ++++++--
2 files changed, 9 insertions(+), 2 deletions(-)
@@ -12,6 +12,9 @@ Optional properties: only if property "phy-reset-gpios" is available. Missing the property will have the duration be 1 millisecond. Numbers greater than 1000 are invalid and 1 millisecond will be used instead.+- phy-reset-active-low : If present then the reset sequence using the GPIO+ specified in the "phy-reset-gpios" property is reversed (H=reset state,+ L=operation state). - phy-supply : regulator that powers the Ethernet PHY. - phy-handle : phandle to the PHY device connected to this device. - fixed-link : Assume a fixed link. See fixed-link.txt in the same directory.
On Monday 08 February 2016 21:21:13 Bernhard Walle wrote:
We need that for a custom hardware that needs the reverse reset
sequence.
Signed-off-by: Bernhard Walle <redacted>
Why can't this be specified in the gpios property?
Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Andrew Lunn <andrew@lunn.ch> Date: 2016-02-08 21:49:03
On Mon, Feb 08, 2016 at 09:21:13PM +0100, Bernhard Walle wrote:
quoted hunk
We need that for a custom hardware that needs the reverse reset
sequence.
Signed-off-by: Bernhard Walle <redacted>
---
Documentation/devicetree/bindings/net/fsl-fec.txt | 3 +++
drivers/net/ethernet/freescale/fec_main.c | 8 ++++++--
2 files changed, 9 insertions(+), 2 deletions(-)
@@ -12,6 +12,9 @@ Optional properties: only if property "phy-reset-gpios" is available. Missing the property will have the duration be 1 millisecond. Numbers greater than 1000 are invalid and 1 millisecond will be used instead.+- phy-reset-active-low : If present then the reset sequence using the GPIO+ specified in the "phy-reset-gpios" property is reversed (H=reset state,+ L=operation state).
Hi Bernhard
Maybe at the same time add a comment to phy-reset-gpios that the flags
part is ignored, see the none standard phy-reset-active-low property
instead.
Andrew
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Andrew Lunn <andrew@lunn.ch> Date: 2016-02-08 21:51:43
On Mon, Feb 08, 2016 at 10:46:42PM +0100, Arnd Bergmann wrote:
On Monday 08 February 2016 21:21:13 Bernhard Walle wrote:
quoted
We need that for a custom hardware that needs the reverse reset
sequence.
Signed-off-by: Bernhard Walle <redacted>
Why can't this be specified in the gpios property?
Backwards compatibility. The flag has always been ignored until now,
yet various DTs have a flag value which are active low. If suddenly it
worked, various boards would break :-(
Andrew
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Monday 08 February 2016 22:51:38 Andrew Lunn wrote:
On Mon, Feb 08, 2016 at 10:46:42PM +0100, Arnd Bergmann wrote:
quoted
On Monday 08 February 2016 21:21:13 Bernhard Walle wrote:
quoted
We need that for a custom hardware that needs the reverse reset
sequence.
Signed-off-by: Bernhard Walle <redacted>
Why can't this be specified in the gpios property?
Backwards compatibility. The flag has always been ignored until now,
yet various DTs have a flag value which are active low. If suddenly it
worked, various boards would break