From: Nishanth Menon <nm@ti.com>
To: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
Vaishnav Achath <vaishnav.a@ti.com>,
Jared McArthur <j-mcarthur@ti.com>, Bryan Brattlof <bb@ti.com>,
Dhruva Gole <d-gole@ti.com>
Subject: [PATCH 0/3] arm64: dts: ti: k3-am62p/j722s: Add gpio-ranges properties
Date: Tue, 18 Jun 2024 12:31:20 -0500 [thread overview]
Message-ID: <20240618173123.2592074-1-nm@ti.com> (raw)
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
next reply other threads:[~2024-06-18 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 17:31 Nishanth Menon [this message]
2024-06-18 17:31 ` [PATCH 1/3] arm64: dts: ti: k3-pinctrl: Define a generic GPIO MUX Mode Nishanth Menon
2024-06-19 4:52 ` Dhruva Gole
2024-06-19 13:02 ` Nishanth Menon
2024-06-18 17:31 ` [PATCH 2/3] arm64: dts: ti: k3-am62p: Add gpio-ranges properties Nishanth Menon
2024-06-19 8:00 ` Dhruva Gole
2024-06-18 17:31 ` [PATCH 3/3] arm64: dts: ti: k3-j722s: " Nishanth Menon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240618173123.2592074-1-nm@ti.com \
--to=nm@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-mcarthur@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vaishnav.a@ti.com \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox