linux-kernel - Re: [PATCH V2 0/3] arm64: dts: ti: k3-am62p/j722s: Add gpio-ranges properties

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: <171984950185.3152309.941998277550954713.b4-ty@ti.com>
Date: Wed, 3 Jul 2024 10:05:11 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Conor Dooley <conor+dt@...nel.org>,
        Krzysztof Kozlowski
	<krzk+dt@...nel.org>,
        Rob Herring <robh@...nel.org>, Nishanth Menon
	<nm@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, <linux-kernel@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
        Tero
 Kristo <kristo@...nel.org>, Vaishnav Achath <vaishnav.a@...com>,
        Jared
 McArthur <j-mcarthur@...com>, Bryan Brattlof <bb@...com>,
        Dhruva Gole
	<d-gole@...com>
Subject: Re: [PATCH V2 0/3] arm64: dts: ti: k3-am62p/j722s: Add gpio-ranges properties

Hi Nishanth Menon,

On Thu, 27 Jun 2024 11:25:36 -0500, Nishanth Menon wrote:
> This series was tested on BeagleY-AI[1] using the script[2].
> 
> This allows gpiod to request for a gpio that is not in the default GPIO
> mux mode and the framework controls the mux over to required GPIO mode.
> 
> The series is based off next-20240617.
> 
> [...]

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

[1/3] arm64: dts: ti: k3-pinctrl: Define a generic GPIO MUX Mode
      commit: 50d9981fa12212cdc0110c42db0411209bb5d765
[2/3] arm64: dts: ti: k3-am62p: Add gpio-ranges properties
      commit: d72d73a44c3c98109764bfb56c329cd628c518cc
[3/3] arm64: dts: ti: k3-j722s: Add gpio-ranges properties
      commit: 90d3d2eed998fef92f7bbc8557a843360516ccee

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