Netdev List
 help / color / mirror / Atom feed
From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "olteanv@gmail.com" <olteanv@gmail.com>
Cc: "hauke@hauke-m.de" <hauke@hauke-m.de>,
	"andrew@lunn.ch" <andrew@lunn.ch>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"daniel@makrotopia.org" <daniel@makrotopia.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>
Subject: Re: [PATCH v3 2/2] net: dsa: mxl-gsw1xx: Support R(G)MII slew rate configuration
Date: Mon, 5 Jan 2026 21:00:27 +0000	[thread overview]
Message-ID: <ac648a7e6883e68026f67ae0544b544614006d8f.camel@siemens.com> (raw)
In-Reply-To: <20260105193016.jlnsvgavlilhync7@skbuf>

Hi Vladimir,

On Mon, 2026-01-05 at 21:30 +0200, Vladimir Oltean wrote:
> > +	return regmap_update_bits(gsw1xx_priv->shell, GSW1XX_SHELL_RGMII_SLEW_CFG,
> > +				  RGMII_SLEW_CFG_DRV_TXD | RGMII_SLEW_CFG_DRV_TXC,
> > +				  (RGMII_SLEW_CFG_DRV_TXD | RGMII_SLEW_CFG_DRV_TXC) * rate);
> 
> I don't have a particularly strong EE background, but my understanding
> is this:
> 
> RGMII MACs provide individual slew rate configuration for TXD[3:0] and
> for TX_CLK because normally, you'd want to focus on the TX_CLK slew rate
> (in the sense of reducing EMI) more than on the TXD[3:0] slew rate.
> This is for 2 reasons:
> (1) the EMI noise produced by TX_CLK is in a much narrower spectrum
>     (runs at fixed 125/25/2.5 MHz) than TXD[3:0] (pseudo-random data).
> (2) reducing the slew rate for TXD[3:0] risks introducing inter-symbol
>     interference, risk which does not exist for TX_CLK
> 
> Your dt-binding does not permit configuring the slew rates separately,
> even though the hardware permits that. Was it intentional?

thanks for the hint! This is definitely something I need to discuss with HW
colleagues and get back to you!

-- 
Alexander Sverdlin
Siemens AG
www.siemens.com

  reply	other threads:[~2026-01-05 21:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 17:53 [PATCH net-next v3 0/2] dsa: mxl-gsw1xx: Support R(G)MII slew rate configuration A. Sverdlin
2026-01-05 17:53 ` [PATCH v3 1/2] dt-bindings: net: dsa: lantiq,gswip: add MaxLinear R(G)MII slew rate A. Sverdlin
2026-01-05 18:00   ` Sverdlin, Alexander
2026-01-05 23:56     ` Jakub Kicinski
2026-01-05 17:53 ` [PATCH v3 2/2] net: dsa: mxl-gsw1xx: Support R(G)MII slew rate configuration A. Sverdlin
2026-01-05 19:30   ` Vladimir Oltean
2026-01-05 21:00     ` Sverdlin, Alexander [this message]
2026-01-06  9:41       ` Sverdlin, Alexander
2026-01-06 23:05         ` Vladimir Oltean

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=ac648a7e6883e68026f67ae0544b544614006d8f.camel@siemens.com \
    --to=alexander.sverdlin@siemens.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=hauke@hauke-m.de \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --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