From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<josua@solid-run.com>, <w.egorov@phytec.de>,
<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>, <afd@ti.com>,
<u-kumar1@ti.com>, <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>, <s-vadapalli@ti.com>
Subject: Re: [PATCH v2 00/13] TI: K3 DTS: fix USB Clocking for Compliance
Date: Thu, 7 May 2026 12:14:54 +0530 [thread overview]
Message-ID: <0e9e5de7-b456-4da3-8165-8ed7d66f2671@ti.com> (raw)
In-Reply-To: <CAOCHtYjJRmr5LhRePqaOomjVHb=o+B8-3+6BN89Xx9erwRdcng@mail.gmail.com>
On 06/05/26 22:37, Robert Nelson wrote:
> On Wed, May 6, 2026 at 9:08 AM Siddharth Vadapalli <s-vadapalli@ti.com> wrote:
>>
>> Hello,
>>
>> This series enables Internal Spread Spectrum Clocking (SSC) for USB
>> SuperSpeed configuration. This is mandated by the USB Specification
>> section 6.5.3 Normative Spread Spectrum Clocking (SSC).
>>
>> Series has been posted as individual patches for respective boards since
>> the Fixes tag is different for each board and needs to be backported via
>> stable.
>
> While yes, that's true for stable branches. Since these are so
> similar, wouldn't it be best to push them to the board soc family
> headers?
I see individual patches per board+SoC combination for new features as
well. So having individual patches for Fixes seems to be preferred given
that squashing all Fixes tags into a single patch doesn't make it easy for
backporting and reverting in case of issues is also easier for individual
patches.
>
> (Either way, I'll be backporting these for Beagle. ;) )
Thank you.
Regards,
Siddharth.
next prev parent reply other threads:[~2026-05-07 6:43 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
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 [this message]
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=0e9e5de7-b456-4da3-8165-8ed7d66f2671@ti.com \
--to=s-vadapalli@ti.com \
--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=srk@ti.com \
--cc=stable@vger.kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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