From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Marek Vasut <marek.vasut@mailbox.org>,
netdev@vger.kernel.org, "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>,
devicetree@vger.kernel.org
Subject: Re: [net-next,PATCH 3/3] net: phy: realtek: Add property to enable SSC
Date: Wed, 3 Dec 2025 17:35:03 +0000 [thread overview]
Message-ID: <aTB0x6JGcGUM04UX@shell.armlinux.org.uk> (raw)
In-Reply-To: <20251203123430.zq7sjxfwb5kkff7q@skbuf>
On Wed, Dec 03, 2025 at 02:34:30PM +0200, Vladimir Oltean wrote:
> On Wed, Dec 03, 2025 at 10:18:35AM +0000, Russell King (Oracle) wrote:
> > On Sun, Nov 30, 2025 at 01:58:34AM +0100, Marek Vasut wrote:
> > > Add support for spread spectrum clocking (SSC) on RTL8211F(D)(I)-CG,
> > > RTL8211FS(I)(-VS)-CG, RTL8211FG(I)(-VS)-CG PHYs. The implementation
> > > follows EMI improvement application note Rev. 1.2 for these PHYs.
> > >
> > > The current implementation enables SSC for both RXC and SYSCLK clock
> > > signals. Introduce new DT property 'realtek,ssc-enable' to enable the
> > > SSC mode.
> >
> > Should there be separate properties for CLKOUT SSC enable and RXC SSC
> > enable?
>
> That's what we're trying to work out. I was going to try and give an
> example (based on stmmac) why you wouldn't want RXC SSC but you'd still
> want CLKOUT SSC, but it doesn't seem to hold water based on your feedback.
> Having one device tree property to control both clocks is a bit simpler.
The problem I see is that if we introduce a single property for both,
we then need to maintain this single property ad infinitum. If we
later find that we need separate control, we could end up with three
properties - the combined one, and two for individual controls.
If we are to go with a single property, then I think we should have at
least discussed what we would do if we need separate control.
If we go with two properties now, then we don't have to consider this,
and we will only ever have the two properties rather than three.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-12-03 17:35 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
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) [this message]
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=aTB0x6JGcGUM04UX@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--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=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).