[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240618173123.2592074-1-nm@ti.com>
Date: Tue, 18 Jun 2024 12:31:20 -0500
From: Nishanth Menon <nm@...com>
To: Conor Dooley <conor+dt@...nel.org>,
Krzysztof Kozlowski
<krzk+dt@...nel.org>,
Rob Herring <robh@...nel.org>
CC: <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Tero Kristo <kristo@...nel.org>, Vignesh Raghavendra <vigneshr@...com>,
Nishanth Menon <nm@...com>, Vaishnav
Achath <vaishnav.a@...com>,
Jared McArthur <j-mcarthur@...com>, Bryan
Brattlof <bb@...com>,
Dhruva Gole <d-gole@...com>
Subject: [PATCH 0/3] arm64: dts: ti: k3-am62p/j722s: Add gpio-ranges properties
Hi,
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.
NOTE: there is also a dtb_warning that is added, which as far as I can
see is either a dtschema bug or a pinctrl-single binding error. more
information in [3]
Jared McArthur (1):
arm64: dts: ti: k3-j722s: Add gpio-ranges properties
Nishanth Menon (2):
arm64: dts: ti: k3-pinctrl: Define a generic GPIO MUX Mode
arm64: dts: ti: k3-am62p: Add gpio-ranges properties
arch/arm64/boot/dts/ti/k3-am62p-main.dtsi | 14 ++++++++++++++
arch/arm64/boot/dts/ti/k3-am62p-mcu.dtsi | 10 ++++++++++
arch/arm64/boot/dts/ti/k3-j722s.dtsi | 17 +++++++++++++++++
arch/arm64/boot/dts/ti/k3-pinctrl.h | 2 ++
4 files changed, 43 insertions(+)
base-commit: 76db4c64526c5e8ba0f56ad3d890dce8f9b00bbc
[1] https://www.beagleboard.org/boards/beagley-ai
[2] https://gist.github.com/nmenon/4973770cf0df3f02c2e4f7f3d048d80d
[3] https://lore.kernel.org/r/20240618165102.2380159-1-nm@ti.com
--
2.43.0
Powered by blists - more mailing lists