From: Krzysztof Kozlowski <krzk@kernel.org>
To: Marek Vasut <marek.vasut@mailbox.org>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Aleksander Jan Bajkowski <olek2@wp.pl>,
Andrew Lunn <andrew@lunn.ch>, Conor Dooley <conor+dt@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Michael Klein <michael@fossekall.de>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
devicetree@vger.kernel.org
Subject: Re: [net-next,PATCH 2/3] dt-bindings: net: realtek,rtl82xx: Document realtek,ssc-enable property
Date: Wed, 3 Dec 2025 08:56:24 +0100 [thread overview]
Message-ID: <67b5f5b5-caf9-4dcc-b84d-a7ce338fc25d@kernel.org> (raw)
In-Reply-To: <4aaa73b4-3a2a-44f6-ad81-74c30be13431@mailbox.org>
On 03/12/2025 02:30, Marek Vasut wrote:
> On 12/1/25 8:20 AM, Krzysztof Kozlowski wrote:
>> On 30/11/2025 14:41, Marek Vasut wrote:
>>> On 11/30/25 9:20 AM, Krzysztof Kozlowski wrote:
>>>
>>> Hello Krzysztof,
>>>
>>>>> diff --git a/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml b/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml
>>>>> index eafcc2f3e3d66..f1bd0095026be 100644
>>>>> --- a/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml
>>>>> +++ b/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml
>>>>> @@ -50,6 +50,11 @@ properties:
>>>>> description:
>>>>> Disable CLKOUT clock, CLKOUT clock default is enabled after hardware reset.
>>>>>
>>>>> + realtek,ssc-enable:
>>>>> + type: boolean
>>>>> + description:
>>>>> + Enable SSC mode, SSC mode default is disabled after hardware reset.
>>>>
>>>> I don't want more SSC properties. We already had a big discussions about
>>>> it - one person pushing vendor property and only shortly after we learnt
>>>> that more vendors want it and they are actually working on this.
>>> What kind of a property would you propose I use for this ?
>>
>> I don't know, please look at existing work around SSC from Peng. If
>> nothing is applicable, this should be explained somewhere.
>
> The work from Peng you refer to (I guess) is this "assigned-clock-sscs"
> property ? This is not applicable, because this is a boolean property of
> the PHY here, the clock does not expose those clock via the clock API.
OK, please mention this in the commit msg - that assigned-clock-sscs is
not applicable, because these are clocks not exposed outside.
I saw already brcm,enable-ssc property, so use rather "realtek,enable-ssc".
>
> However, I can call the property "ssc-enable" without the realtek,
> vendor prefix ?
I think no, I am not so sure how generic it would be to cover all
existing cases. Some devices, e.g. cdns, defines the mode of SSC, so
uses an enum.
>
> The remaining question is, should I have one property "ssc-enable" to
> control all SSC in the PHY or one for each bit "realtek,ssc-enable-rxc"
> / "realtek,ssc-enable-clkout" ?
I don't know. Can they be enabled independently? Does it make sense for
the hardware to have different choices?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-03 7:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-30 0:58 [net-next,PATCH 1/3] dt-bindings: net: realtek,rtl82xx: Keep property list sorted Marek Vasut
2025-11-30 0:58 ` [net-next,PATCH 2/3] dt-bindings: net: realtek,rtl82xx: Document realtek,ssc-enable property Marek Vasut
2025-11-30 1:43 ` Andrew Lunn
2025-11-30 13:43 ` Marek Vasut
2025-11-30 2:29 ` Rob Herring (Arm)
2025-11-30 8:20 ` Krzysztof Kozlowski
2025-11-30 13:41 ` Marek Vasut
2025-12-01 7:20 ` Krzysztof Kozlowski
2025-12-03 1:30 ` Marek Vasut
2025-12-03 7:56 ` Krzysztof Kozlowski [this message]
2025-12-03 20:16 ` Marek Vasut
2025-11-30 0:58 ` [net-next,PATCH 3/3] net: phy: realtek: Add property to enable SSC Marek Vasut
2025-12-03 9:42 ` Vladimir Oltean
2025-12-03 10:16 ` Russell King (Oracle)
2025-12-03 20:46 ` Marek Vasut
2025-12-03 13:01 ` Ivan Galkin
2025-12-03 20:51 ` Marek Vasut
2025-12-03 14:18 ` Ivan Galkin
2025-12-03 20:56 ` Marek Vasut
2025-12-03 20:17 ` Marek Vasut
2025-12-03 10:18 ` Russell King (Oracle)
2025-12-03 12:34 ` Vladimir Oltean
2025-12-03 17:35 ` Russell King (Oracle)
2025-12-03 19:21 ` Marek Vasut
2025-11-30 2:29 ` [net-next,PATCH 1/3] dt-bindings: net: realtek,rtl82xx: Keep property list sorted Rob Herring (Arm)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67b5f5b5-caf9-4dcc-b84d-a7ce338fc25d@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marek.vasut@mailbox.org \
--cc=michael@fossekall.de \
--cc=netdev@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=vladimir.oltean@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).