linux-kernel - Re: [PATCH v2] arm64: dts: ti: k3-j7200: Fix register map for main domain pmx

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: <173021674662.3859929.17306406309658098523.b4-ty@ti.com>
Date: Wed, 30 Oct 2024 10:22:24 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <mranostay@...com>,
        <conor+dt@...nel.org>, <krzk+dt@...nel.org>, <robh@...nel.org>,
        <kristo@...nel.org>, <nm@...com>, Aniket Limaye <a-limaye@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, <u-kumar1@...com>,
        Jared McArthur
	<j-mcarthur@...com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-j7200: Fix register map for main domain pmx

Hi Aniket Limaye,

On Thu, 26 Sep 2024 15:55:33 +0530, Aniket Limaye wrote:
> Commit 0d0a0b441346 ("arm64: dts: ti: k3-j7200: fix main pinmux
> range") split the main_pmx0 into two nodes: main_pmx0 and main_pmx1
> due to a non-addressable region, but incorrectly represented the
> ranges. As a result, the memory map for the pinctrl is incorrect. Fix
> this by introducing the correct ranges.
> 
> The ranges are taken from the J7200 TRM [1] (Table 5-695. CTRL_MMR0
> Registers).
> 
> [...]

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

[1/1] arm64: dts: ti: k3-j7200: Fix register map for main domain pmx
      commit: b7af8b4acb3e08c710cd48f098ce8cd07cf43a1e

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