lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <67f96fd7-d2f7-444a-b448-55883f8e7fc2@mailbox.org>
Date: Sun, 30 Nov 2025 14:43:08 +0100
From: Marek Vasut <marek.vasut@...lbox.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
 Aleksander Jan Bajkowski <olek2@...pl>, Conor Dooley <conor+dt@...nel.org>,
 Eric Dumazet <edumazet@...gle.com>, Florian Fainelli <f.fainelli@...il.com>,
 Heiner Kallweit <hkallweit1@...il.com>, Jakub Kicinski <kuba@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Michael Klein <michael@...sekall.de>, Paolo Abeni <pabeni@...hat.com>,
 Rob Herring <robh@...nel.org>, Russell King <linux@...linux.org.uk>,
 Vladimir Oltean <vladimir.oltean@....com>, devicetree@...r.kernel.org
Subject: Re: [net-next,PATCH 2/3] dt-bindings: net: realtek,rtl82xx: Document
 realtek,ssc-enable property

On 11/30/25 2:43 AM, Andrew Lunn wrote:

Hello Andrew,

>> 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.
> 
> Spread Spectrum Clocking is a generic concept, applicable to more than
> Ethernet PHYs. Do we really need a vendor property for this? Or is
> there a generic property already?
Let's see what Krzysztof has to say about this, I am fine with generic 
property ... unless it would be desirable to control the RXC and SYSCLK 
spread spectrum separately ?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ