From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: 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>,
Ivan Galkin <ivan.galkin@axis.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>,
devicetree@vger.kernel.org
Subject: Re: [net-next,PATCH v3 3/3] net: phy: realtek: Add property to enable SSC
Date: Sat, 28 Feb 2026 13:02:57 +0200 [thread overview]
Message-ID: <20260228110257.bowskqkl3ujv3ri6@skbuf> (raw)
In-Reply-To: <d6c83860-85ba-4a99-b2ab-486ad040ea55@mailbox.org>
On Sat, Feb 28, 2026 at 04:57:25AM +0100, Marek Vasut wrote:
> On 2/4/26 3:25 PM, Marek Vasut wrote:
> > On 12/18/25 6:36 PM, 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 DT properties 'realtek,clkout-ssc-enable',
> > > 'realtek,rxc-ssc-enable' and 'realtek,sysclk-ssc-enable' which control
> > > CLKOUT, RXC and SYSCLK SSC spread spectrum clocking enablement on these
> > > signals.
> > >
> > > Signed-off-by: Marek Vasut <marek.vasut@mailbox.org>
> > Is there anything that should be adjusted in these patches ?
>
> How can we proceed here ?
The state in Patchwork is Deferred. You were told that you submitted the
series in the merge window.
https://patchwork.kernel.org/project/netdevbpf/patch/20251218173718.12878-1-marek.vasut@mailbox.org/
It won't be applied as is (needs to be build-tested again on v7.0-rc...),
so please resend.
next prev parent reply other threads:[~2026-02-28 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 17:36 [net-next,PATCH v3 1/3] dt-bindings: net: realtek,rtl82xx: Keep property list sorted Marek Vasut
2025-12-18 17:36 ` [net-next,PATCH v3 2/3] dt-bindings: net: realtek,rtl82xx: Document realtek,*-ssc-enable property Marek Vasut
2025-12-18 17:36 ` [net-next,PATCH v3 3/3] net: phy: realtek: Add property to enable SSC Marek Vasut
2026-02-04 14:25 ` Marek Vasut
2026-02-28 3:57 ` Marek Vasut
2026-02-28 11:02 ` Vladimir Oltean [this message]
2026-03-21 18:59 ` Marek Vasut
2025-12-19 9:36 ` [net-next,PATCH v3 1/3] dt-bindings: net: realtek,rtl82xx: Keep property list sorted Paolo Abeni
2025-12-29 23:35 ` 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=20260228110257.bowskqkl3ujv3ri6@skbuf \
--to=vladimir.oltean@nxp.com \
--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=ivan.galkin@axis.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 \
/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