linux-kernel - Re: [PATCH] arm64: dts: ti: k3-am69-sk: Switch to PCIe Multilink + USB configuration

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <175589190685.650517.15346755331299004953.b4-ty@ti.com>
Date: Fri, 22 Aug 2025 14:45:36 -0500
From: Nishanth Menon <nm@...com>
To: <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
        <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
        Siddharth Vadapalli
	<s-vadapalli@...com>
CC: Nishanth Menon <nm@...com>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
        <srk@...com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am69-sk: Switch to PCIe Multilink + USB configuration

Hi Siddharth Vadapalli,

On Tue, 19 Aug 2025 16:27:00 +0530, Siddharth Vadapalli wrote:
> The SERDES0 instance of SERDES on the AM69 SoC is a Cadence Torrent SERDES
> and it has 4 lanes which are allocated in the following manner:
> Lane0 and Lane1 to PCIe1
> Lane2 to PCIe3
> Lane3 to USB0
> 
> Until [0], the Cadence Torrent SERDES driver only supported configuring
> the SERDES for a PCIe + USB configuration whereby all lanes of the
> SERDES configured for PCIe will operate at the same speed. As a result,
> PCIe1 and PCIe3 instances of PCIe will either fall down to a common
> speed based on the PCIe peers that they are each connected to, or, the
> PCIe link could fail to be setup.
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/1] arm64: dts: ti: k3-am69-sk: Switch to PCIe Multilink + USB configuration
      commit: 76397d42e248335aa41acbf0af6d096220605202

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource