linux-kernel - Re: [PATCH] arm64: dts: ti: k3-j722s: Fix main domain GPIO count

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 for Android: free password hash cracker in your pocket

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

Message-ID: <171826022272.240984.17084650953206943074.b4-ty@ti.com>
Date: Thu, 13 Jun 2024 13:16:41 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <kristo@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
        <conor+dt@...nel.org>, Vaishnav Achath <vaishnav.a@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, <linux-kernel@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <j-choudhary@...com>, <u-kumar1@...com>,
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-j722s: Fix main domain GPIO count

Hi Vaishnav Achath,

On Tue, 07 May 2024 16:03:32 +0530, Vaishnav Achath wrote:
> J722S does not pin out all of the GPIO same as AM62P and have
> more number of GPIO on the main_gpio1 instance. Fix the GPIO
> count on both instances by overriding the ti,ngpio property.
> 
> Fixes: ea55b9335ad8 ("arm64: dts: ti: Introduce J722S family of SoCs")
> 
> More details at J722S/AM67 Datasheet (Section 5.3.11, GPIO):
> 	https://www.ti.com/lit/ds/symlink/am67.pdf
> 
> [...]

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

[1/1] arm64: dts: ti: k3-j722s: Fix main domain GPIO count
      commit: 2cdf63e73415ce6c8f6b3397cdc91d5f928855f9

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