Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1573687 > unrolled thread

[PATCH] Documentation: devicetree: Add PHY no lane swap binding

Started byLukasz Majewski <lukma@denx.de>
First post2017-02-04 16:50 +0100
Last post2017-02-06 19:00 +0100
Articles 6 — 3 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH] Documentation: devicetree: Add PHY no lane swap binding Lukasz Majewski <lukma@denx.de> - 2017-02-04 16:50 +0100
    Re: [PATCH] Documentation: devicetree: Add PHY no lane swap binding Andrew Lunn <andrew@lunn.ch> - 2017-02-04 18:30 +0100
      Re: [PATCH] Documentation: devicetree: Add PHY no lane swap binding Florian Fainelli <f.fainelli@gmail.com> - 2017-02-04 22:40 +0100
        Re: [PATCH] Documentation: devicetree: Add PHY no lane swap binding Lukasz Majewski <lukma@denx.de> - 2017-02-06 15:20 +0100
          Re: [PATCH] Documentation: devicetree: Add PHY no lane swap binding Andrew Lunn <andrew@lunn.ch> - 2017-02-06 15:40 +0100
          Re: [PATCH] Documentation: devicetree: Add PHY no lane swap binding Florian Fainelli <f.fainelli@gmail.com> - 2017-02-06 19:00 +0100

#1573687 — [PATCH] Documentation: devicetree: Add PHY no lane swap binding

FromLukasz Majewski <lukma@denx.de>
Date2017-02-04 16:50 +0100
Subject[PATCH] Documentation: devicetree: Add PHY no lane swap binding
Message-ID<t7aL7-2s6-3@gated-at.bofh.it>
Add the documentation to avoid PHY lane swapping. This is a boolean
entry to notify the phy device drivers that the TX/RX lanes NO need
to be swapped.
The use case for this binding mostly happens after wrong HW
configuration of PHY IC during bootstrap.

Signed-off-by: Lukasz Majewski <lukma@denx.de>
---
 Documentation/devicetree/bindings/net/phy.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/devicetree/bindings/net/phy.txt b/Documentation/devicetree/bindings/net/phy.txt
index fb5056b..5e25bc9 100644
--- a/Documentation/devicetree/bindings/net/phy.txt
+++ b/Documentation/devicetree/bindings/net/phy.txt
@@ -39,6 +39,10 @@ Optional Properties:
 - enet-phy-lane-swap: If set, indicates the PHY will swap the TX/RX lanes to
   compensate for the board being designed with the lanes swapped.
 
+- enet-phy-lane-no-swap: If set, indicates that PHY will disable swap of the
+  TX/RX lanes. This binding allows the PHY to work correcly after e.g. wrong
+  bootstrap configuration caused by issues in PCB layout design.
+
 - eee-broken-100tx:
 - eee-broken-1000t:
 - eee-broken-10gt:
-- 
2.1.4

[toc] | [next] | [standalone]


#1573716

FromAndrew Lunn <andrew@lunn.ch>
Date2017-02-04 18:30 +0100
Message-ID<t7cjT-3BN-17@gated-at.bofh.it>
In reply to#1573687
On Sat, Feb 04, 2017 at 04:47:47PM +0100, Lukasz Majewski wrote:
> Add the documentation to avoid PHY lane swapping. This is a boolean
> entry to notify the phy device drivers that the TX/RX lanes NO need

that the TX/RX lanes should not be swapped.

> to be swapped.
> The use case for this binding mostly happens after wrong HW
> configuration of PHY IC during bootstrap.
> 
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
> ---
>  Documentation/devicetree/bindings/net/phy.txt | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/net/phy.txt b/Documentation/devicetree/bindings/net/phy.txt
> index fb5056b..5e25bc9 100644
> --- a/Documentation/devicetree/bindings/net/phy.txt
> +++ b/Documentation/devicetree/bindings/net/phy.txt
> @@ -39,6 +39,10 @@ Optional Properties:
>  - enet-phy-lane-swap: If set, indicates the PHY will swap the TX/RX lanes to
>    compensate for the board being designed with the lanes swapped.
>  
> +- enet-phy-lane-no-swap: If set, indicates that PHY will disable swap of the
> +  TX/RX lanes. This binding allows the PHY to work correcly after e.g. wrong
> +  bootstrap configuration caused by issues in PCB layout design.
> +

We are leaving it undefined what it means if neither
enet-phy-lane-no-swap nor enet-phy-lane-swap properties are present.
Do we want to define this? That the swap should be left untouched by
the driver?

    Andrew

[toc] | [prev] | [next] | [standalone]


#1573759

FromFlorian Fainelli <f.fainelli@gmail.com>
Date2017-02-04 22:40 +0100
Message-ID<t7gdP-6nu-7@gated-at.bofh.it>
In reply to#1573716
Le 02/04/17 à 09:23, Andrew Lunn a écrit :
> On Sat, Feb 04, 2017 at 04:47:47PM +0100, Lukasz Majewski wrote:
>> Add the documentation to avoid PHY lane swapping. This is a boolean
>> entry to notify the phy device drivers that the TX/RX lanes NO need
> 
> that the TX/RX lanes should not be swapped.
> 
>> to be swapped.
>> The use case for this binding mostly happens after wrong HW
>> configuration of PHY IC during bootstrap.
>>
>> Signed-off-by: Lukasz Majewski <lukma@denx.de>
>> ---
>>  Documentation/devicetree/bindings/net/phy.txt | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/net/phy.txt b/Documentation/devicetree/bindings/net/phy.txt
>> index fb5056b..5e25bc9 100644
>> --- a/Documentation/devicetree/bindings/net/phy.txt
>> +++ b/Documentation/devicetree/bindings/net/phy.txt
>> @@ -39,6 +39,10 @@ Optional Properties:
>>  - enet-phy-lane-swap: If set, indicates the PHY will swap the TX/RX lanes to
>>    compensate for the board being designed with the lanes swapped.
>>  
>> +- enet-phy-lane-no-swap: If set, indicates that PHY will disable swap of the
>> +  TX/RX lanes. This binding allows the PHY to work correcly after e.g. wrong
>> +  bootstrap configuration caused by issues in PCB layout design.

s/binding/property/

>> +
> 
> We are leaving it undefined what it means if neither
> enet-phy-lane-no-swap nor enet-phy-lane-swap properties are present.
> Do we want to define this? That the swap should be left untouched by
> the driver?

Since this is a description of the hardware, absence of a properties
should mean that the driver is at freedom to either keep the hardware
defaults, or come up with its own settings that are sensible for that
particular PHY device.

What would you see clarified here?
-- 
Florian

[toc] | [prev] | [next] | [standalone]


#1574814

FromLukasz Majewski <lukma@denx.de>
Date2017-02-06 15:20 +0100
Message-ID<t7Sj7-61m-13@gated-at.bofh.it>
In reply to#1573759
Hi Florian, Andrew,

> Le 02/04/17 à 09:23, Andrew Lunn a écrit :
> > On Sat, Feb 04, 2017 at 04:47:47PM +0100, Lukasz Majewski wrote:
> >> Add the documentation to avoid PHY lane swapping. This is a boolean
> >> entry to notify the phy device drivers that the TX/RX lanes NO need
> > 
> > that the TX/RX lanes should not be swapped.
> > 
> >> to be swapped.
> >> The use case for this binding mostly happens after wrong HW
> >> configuration of PHY IC during bootstrap.
> >>
> >> Signed-off-by: Lukasz Majewski <lukma@denx.de>
> >> ---
> >>  Documentation/devicetree/bindings/net/phy.txt | 4 ++++
> >>  1 file changed, 4 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/net/phy.txt
> >> b/Documentation/devicetree/bindings/net/phy.txt index
> >> fb5056b..5e25bc9 100644 ---
> >> a/Documentation/devicetree/bindings/net/phy.txt +++
> >> b/Documentation/devicetree/bindings/net/phy.txt @@ -39,6 +39,10 @@
> >> Optional Properties:
> >>  - enet-phy-lane-swap: If set, indicates the PHY will swap the
> >> TX/RX lanes to compensate for the board being designed with the
> >> lanes swapped. 
> >> +- enet-phy-lane-no-swap: If set, indicates that PHY will disable
> >> swap of the
> >> +  TX/RX lanes. This binding allows the PHY to work correcly after
> >> e.g. wrong
> >> +  bootstrap configuration caused by issues in PCB layout design.
> 
> s/binding/property/
> 
> >> +
> > 
> > We are leaving it undefined what it means if neither
> > enet-phy-lane-no-swap nor enet-phy-lane-swap properties are present.
> > Do we want to define this? That the swap should be left untouched by
> > the driver?
> 
> Since this is a description of the hardware, absence of a properties
> should mean that the driver is at freedom to either keep the hardware
> defaults, or come up with its own settings that are sensible for that
> particular PHY device.
> 
> What would you see clarified here?

Any more comments to this patch?

Is the explanation informative enough?


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de

[toc] | [prev] | [next] | [standalone]


#1574843

FromAndrew Lunn <andrew@lunn.ch>
Date2017-02-06 15:40 +0100
Message-ID<t7SCv-68H-41@gated-at.bofh.it>
In reply to#1574814
> > Since this is a description of the hardware, absence of a properties
> > should mean that the driver is at freedom to either keep the hardware
> > defaults, or come up with its own settings that are sensible for that
> > particular PHY device.
> > 
> > What would you see clarified here?
> 
> Any more comments to this patch?

Nope.

	Andrew

[toc] | [prev] | [next] | [standalone]


#1575035

FromFlorian Fainelli <f.fainelli@gmail.com>
Date2017-02-06 19:00 +0100
Message-ID<t7VK2-8by-7@gated-at.bofh.it>
In reply to#1574814
On 02/06/2017 06:15 AM, Lukasz Majewski wrote:
> Hi Florian, Andrew,
> 
>> Le 02/04/17 à 09:23, Andrew Lunn a écrit :
>>> On Sat, Feb 04, 2017 at 04:47:47PM +0100, Lukasz Majewski wrote:
>>>> Add the documentation to avoid PHY lane swapping. This is a boolean
>>>> entry to notify the phy device drivers that the TX/RX lanes NO need
>>>
>>> that the TX/RX lanes should not be swapped.
>>>
>>>> to be swapped.
>>>> The use case for this binding mostly happens after wrong HW
>>>> configuration of PHY IC during bootstrap.
>>>>
>>>> Signed-off-by: Lukasz Majewski <lukma@denx.de>
>>>> ---
>>>>  Documentation/devicetree/bindings/net/phy.txt | 4 ++++
>>>>  1 file changed, 4 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/net/phy.txt
>>>> b/Documentation/devicetree/bindings/net/phy.txt index
>>>> fb5056b..5e25bc9 100644 ---
>>>> a/Documentation/devicetree/bindings/net/phy.txt +++
>>>> b/Documentation/devicetree/bindings/net/phy.txt @@ -39,6 +39,10 @@
>>>> Optional Properties:
>>>>  - enet-phy-lane-swap: If set, indicates the PHY will swap the
>>>> TX/RX lanes to compensate for the board being designed with the
>>>> lanes swapped. 
>>>> +- enet-phy-lane-no-swap: If set, indicates that PHY will disable
>>>> swap of the
>>>> +  TX/RX lanes. This binding allows the PHY to work correcly after
>>>> e.g. wrong
>>>> +  bootstrap configuration caused by issues in PCB layout design.
>>
>> s/binding/property/
>>
>>>> +
>>>
>>> We are leaving it undefined what it means if neither
>>> enet-phy-lane-no-swap nor enet-phy-lane-swap properties are present.
>>> Do we want to define this? That the swap should be left untouched by
>>> the driver?
>>
>> Since this is a description of the hardware, absence of a properties
>> should mean that the driver is at freedom to either keep the hardware
>> defaults, or come up with its own settings that are sensible for that
>> particular PHY device.
>>
>> What would you see clarified here?
> 
> Any more comments to this patch?
> 
> Is the explanation informative enough?

Please resubmit as part of your PHY driver changes, and change binding
in the description above for property.
-- 
Florian

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web