linux-kernel - Re: [PATCH] arm64: dts: ti: k3-am62a7-sk: fix pinmux for main

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: <175205725857.918402.13683830653184738148.b4-ty@ti.com>
Date: Fri, 11 Jul 2025 10:33:11 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>,
        Rob Herring
	<robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley
	<conor+dt@...nel.org>, Bryan Brattlof <bb@...com>
CC: Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, Hong Guan <hguan@...com>,
        <stable@...r.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62a7-sk: fix pinmux for main_uart1

Hi Bryan Brattlof,

On Mon, 07 Jul 2025 11:55:13 -0500, Bryan Brattlof wrote:
> The &main_uart1, which is reserved for TIFS firmware traces, is routed
> to the onboard FT4232 via a FET swich which is connected to pin A21 and

Reword this bit locally along with s/swich/switch.

>
> B21 of the SoC and not E17 and C17. Fix it.
> 
> 

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

[1/1] arm64: dts: ti: k3-am62a7-sk: fix pinmux for main_uart1
      commit: 8e44ac61abaae56fc6eb537a04ed78b458c5b984

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
--
Vignesh