linux-kernel - Re: [PATCH v2] arm64: dts: ti: k3-j721e-sk: Fix pinmux for pin Y1 used by power regulator

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: <176373265680.739386.4552474353060268697.b4-ty@ti.com>
Date: Fri, 21 Nov 2025 19:19:17 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <kristo@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
	<conor+dt@...nel.org>, <y-abhilashchandra@...com>, <u-kumar1@...com>,
	Siddharth Vadapalli <s-vadapalli@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, <stable@...r.kernel.org>,
	<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>, <srk@...com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-j721e-sk: Fix pinmux for pin Y1 used by power regulator

Hi Siddharth Vadapalli,

On Wed, 19 Nov 2025 21:31:05 +0530, Siddharth Vadapalli wrote:
> The SoC pin Y1 is incorrectly defined in the WKUP Pinmux device-tree node
> (pinctrl@...1c000) leading to the following silent failure:
> 
>     pinctrl-single 4301c000.pinctrl: mux offset out of range: 0x1dc (0x178)
> 
> According to the datasheet for the J721E SoC [0], the pin Y1 belongs to the
> MAIN Pinmux device-tree node (pinctrl@...000). This is confirmed by the
> address of the pinmux register for it on page 142 of the datasheet which is
> 0x00011C1DC.
> 
> [...]

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

[1/1] arm64: dts: ti: k3-j721e-sk: Fix pinmux for pin Y1 used by power regulator
      commit: 51f89c488f2ecc020f82bfedd77482584ce8027a

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