[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d48e5ef4-6d5b-0977-ed45-de810e42356c@ti.com>
Date: Thu, 15 Sep 2022 10:58:39 +0530
From: Siddharth Vadapalli <s-vadapalli@...com>
To: Rob Herring <robh@...nel.org>
CC: <lee.jones@...aro.org>, <krzysztof.kozlowski@...aro.org>,
<krzysztof.kozlowski+dt@...aro.org>, <kishon@...com>,
<vkoul@...nel.org>, <dan.carpenter@...cle.com>,
<grygorii.strashko@...com>, <rogerq@...nel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-phy@...ts.infradead.org>,
<linux-arm-kernel@...ts.infradead.org>, <sjakhade@...ence.com>,
<s-vadapalli@...com>
Subject: Re: [PATCH 1/6] dt-bindings: phy: ti: phy-gmii-sel: Add bindings for
J721e
Hello Rob,
On 14/09/22 21:45, Rob Herring wrote:
> On Wed, Sep 14, 2022 at 03:09:06PM +0530, Siddharth Vadapalli wrote:
>> TI's J721e SoC supports additional PHY modes like QSGMII and SGMII
>> that are not supported on earlier SoCs. Add a compatible for it.
>>
>> Extend ti,qsgmii-main-ports property to support selection of upto
>> two main ports at once across the two QSGMII interfaces.
>>
>> Signed-off-by: Siddharth Vadapalli <s-vadapalli@...com>
>> ---
>> .../bindings/phy/ti,phy-gmii-sel.yaml | 52 ++++++++++++++++---
>> 1 file changed, 46 insertions(+), 6 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/phy/ti,phy-gmii-sel.yaml b/Documentation/devicetree/bindings/phy/ti,phy-gmii-sel.yaml
>> index da7cac537e15..1e19efab018b 100644
>> --- a/Documentation/devicetree/bindings/phy/ti,phy-gmii-sel.yaml
>> +++ b/Documentation/devicetree/bindings/phy/ti,phy-gmii-sel.yaml
>> @@ -54,6 +54,7 @@ properties:
>> - ti,dm814-phy-gmii-sel
>> - ti,am654-phy-gmii-sel
>> - ti,j7200-cpsw5g-phy-gmii-sel
>> + - ti,j721e-cpsw9g-phy-gmii-sel
>>
>> reg:
>> maxItems: 1
>> @@ -65,12 +66,19 @@ properties:
>> description: |
>> Required only for QSGMII mode. Array to select the port for
>> QSGMII main mode. Rest of the ports are selected as QSGMII_SUB
>> - ports automatically. Any one of the 4 CPSW5G ports can act as the
>> - main port with the rest of them being the QSGMII_SUB ports.
>> - maxItems: 1
>> - items:
>> - minimum: 1
>> - maximum: 4
>> + ports automatically. For J7200 CPSW5G with the compatible:
>> + ti,j7200-cpsw5g-phy-gmii-sel, ti,qsgmii-main-ports is an
>> + array of only one element, which is the port number ranging from
>> + 1 to 4. For J721e CPSW9G with the compatible:
>> + ti,j721e-cpsw9g-phy-gmii-sel, ti,qsgmii-main-ports is an array
>> + of two elements, which corresponds to two potential QSGMII main
>> + ports. The first element and second element of the array can both
>> + range from 1 to 8 each, corresponding to two QSGMII main ports.
>> + For J721e CPSW9G, to configure port 2 as the first QSGMII main
>> + port and port 7 as the second QSGMII main port, we specify:
>> + ti,qsgmii-main-ports = <2>, <7>;
>> + If only one QSGMII main port is desired, mention the same main
>> + port twice.
>
> Two different forms for the same property name is not great. Just make a
> new property if you need something different.
Thank you for reviewing the patch. Based on the discussion for the
previous series at [1], I had planned to reuse the same property
"ti,qsgmii-main-ports" for TI's J721e device too. The reason for this is
that the property represents the same feature on both devices which is
that of the QSGMII main port. The only difference between the two of
them is that J7200's CPSW5G has 4 external ports while J721e's CPSW9G
has 8 external ports. Thus, J7200 can have at most one QSGMII main port
while J721e can have up to two. Adding a new property which describes
the same feature appears to be redundant to me. Please let me know.
[1]-> https://lore.kernel.org/r/48080f45-ea9d-e8dc-7720-ef82fc84e3b3@linaro.org/
Regards,
Siddharth.
Powered by blists - more mailing lists