Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wadim Egorov <w.egorov@phytec.de>
To: Siddharth Vadapalli <s-vadapalli@ti.com>,
	nm@ti.com, vigneshr@ti.com, kristo@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, josua@solid-run.com,
	matthias.schiffer@ew.tq-group.com, d.haller@phytec.de,
	francesco.dolcini@toradex.com, joao.goncalves@toradex.com,
	emanuele.ghidoli@toradex.com, ernest.vanhoecke@toradex.com,
	rogerq@kernel.org, eballetb@redhat.com, robertcnelson@gmail.com,
	afd@ti.com, u-kumar1@ti.com
Cc: stable@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, luis.parga@ti.com,
	srk@ti.com
Subject: Re: [PATCH v2 02/13] arm64: dts: ti: k3-am642-phyboard-electra-rdk: fix USB clocking for compliance
Date: Thu, 7 May 2026 15:56:32 +0300	[thread overview]
Message-ID: <8bff1c7d-e43d-41e6-8b1f-476e8b5caefa@phytec.de> (raw)
In-Reply-To: <20260506141040.1368918-3-s-vadapalli@ti.com>



On 5/6/26 5:09 PM, Siddharth Vadapalli wrote:
> According to section "6.5.3 Normative Spread Spectrum Clocking (SSC)" of
> the USB 3.2 Specification, SSC should be enabled by default. This protects
> against EMI violations. Hence, enable internal SSC for USB SuperSpeed.
> 
> Fixes: c48ac0efe6d7 ("arm64: dts: ti: Add support for phyBOARD-Electra-AM642")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>

Acked-by: Wadim Egorov <w.egorov@phytec.de>

> ---
> 
> v1:
> https://lore.kernel.org/r/20260505110631.1144200-3-s-vadapalli@ti.com/
> No changes since v1.
> 
>  arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts b/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts
> index 793538f94942..a85d7d08bd1b 100644
> --- a/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts
> @@ -439,12 +439,21 @@ &sdhci1 {
>  	status = "okay";
>  };
>  
> +&serdes_wiz0 {
> +	ti,core-clk-sel = <1>;  /* Select internal reference clock */
> +	ti,ssc-enable; /* Enable SSC */
> +	ti,ssc-type = <1>; /* 1 for Downspread */
> +	ti,ssc-frequency-hz = <33000>; /* 33 KHz */
> +	ti,ssc-depth-per-mil = <5>; /* 0.5% depth */
> +};
> +
>  &serdes0 {
>  	serdes0_pcie_usb_link: phy@0 {
>  		reg = <0>;
>  		cdns,num-lanes = <1>;
>  		#phy-cells = <0>;
>  		cdns,phy-type = <PHY_TYPE_USB3>;
> +		cdns,ssc-mode = <2>; /* 2 for internal SSC */
>  		resets = <&serdes_wiz0 1>;
>  	};
>  };



  parent reply	other threads:[~2026-05-07 12:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06 14:09 [PATCH v2 00/13] TI: K3 DTS: fix USB Clocking for Compliance Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 01/13] arm64: dts: ti: k3-am642-hummingboard-t: fix USB clocking for compliance Siddharth Vadapalli
2026-05-06 14:17   ` Josua Mayer
2026-05-07  6:39     ` Siddharth Vadapalli
2026-05-07 15:47       ` Nishanth Menon
2026-05-06 14:09 ` [PATCH v2 02/13] arm64: dts: ti: k3-am642-phyboard-electra-rdk: " Siddharth Vadapalli
2026-05-07  8:25   ` Wadim Egorov
2026-05-07  8:45     ` Siddharth Vadapalli
2026-05-07 15:44       ` Nishanth Menon
2026-05-07 12:56   ` Wadim Egorov [this message]
2026-05-06 14:09 ` [PATCH v2 03/13] arm64: dts: ti: k3-am642-sk: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 04/13] arm64: dts: ti: k3-am642-tqma64xxl: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 05/13] arm64: dts: ti: k3-am68-phyboard-izar: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 06/13] arm64: dts: ti: k3-am68-sk-baseboard: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 07/13] arm64: dts: ti: k3-am69-aquila: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 08/13] arm64: dts: ti: k3-am69-sk: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 09/13] arm64: dts: ti: k3-j721e-beagleboneai64: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 10/13] arm64: dts: ti: k3-j721e-common-proc-board: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 11/13] arm64: dts: ti: k3-j721e-sk: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 12/13] arm64: dts: ti: k3-j722s-evm: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 13/13] arm64: dts: ti: k3-j784s4-j742s2-evm-common: " Siddharth Vadapalli
2026-05-06 17:07 ` [PATCH v2 00/13] TI: K3 DTS: fix USB Clocking for Compliance Robert Nelson
2026-05-07  6:44   ` Siddharth Vadapalli
2026-05-07 15:59     ` Nishanth Menon
2026-05-07 16:24 ` Nishanth Menon

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=8bff1c7d-e43d-41e6-8b1f-476e8b5caefa@phytec.de \
    --to=w.egorov@phytec.de \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=d.haller@phytec.de \
    --cc=devicetree@vger.kernel.org \
    --cc=eballetb@redhat.com \
    --cc=emanuele.ghidoli@toradex.com \
    --cc=ernest.vanhoecke@toradex.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=joao.goncalves@toradex.com \
    --cc=josua@solid-run.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.parga@ti.com \
    --cc=matthias.schiffer@ew.tq-group.com \
    --cc=nm@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=srk@ti.com \
    --cc=stable@vger.kernel.org \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.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