[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5f5f6412-f466-9a3f-3ec7-aa45ab0049c6@linaro.org>
Date: Thu, 1 Jun 2023 18:52:18 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Detlev Casanova <detlev.casanova@...labora.com>,
Andrew Lunn <andrew@...n.ch>
Cc: linux-kernel@...r.kernel.org, Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>, "David S . Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Florian Fainelli <f.fainelli@...il.com>,
netdev@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: net: phy: Support external PHY xtal
On 31/05/2023 20:00, Detlev Casanova wrote:
>>> + clock-names:
>>> + items:
>>> + - const: xtal
>>
>> I don't think xtal is the best of names here. It generally is used as
>> an abbreviation for crystal. And the commit message is about there not
>> being a crystal, but an actual clock.
>>
>> How is this clock named on the datasheet?
>
> In the case of the PHY I used (RTL8211F), it is EXT_CLK. But this must be
> generic to any (ethernet) PHY, so using ext_clk to match it would not be
> good either.
>
> Now this is about having an external clock, so the ext_clk name makes sense in
> this case.
>
> I'm not pushing one name or another, let's use what you feel is more natural.
Just drop the name.
Best regards,
Krzysztof
Powered by blists - more mailing lists