From: <pshete@nvidia.com>
To: <linux-gpio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<arnd@arndb.de>, <bjorn.andersson@oss.qualcomm.com>,
<conor+dt@kernel.org>, <dmitry.baryshkov@oss.qualcomm.com>,
<ebiggers@kernel.org>, <geert@linux-m68k.org>,
<jonathanh@nvidia.com>, <krzk+dt@kernel.org>,
<kuninori.morimoto.gx@renesas.com>, <linusw@kernel.org>,
<luca.weiss@fairphone.com>, <michal.simek@amd.com>,
<prabhakar.mahadev-lad.rj@bp.renesas.com>, <robh@kernel.org>,
<rosenp@gmail.com>, <sven@kernel.org>,
<thierry.reding@kernel.org>, <webgeek1234@gmail.com>
Cc: <pshete@nvidia.com>
Subject: [PATCH 0/6] Add Tegra238 and Tegra264 pinctrl support
Date: Thu, 9 Apr 2026 13:13:34 +0000 [thread overview]
Message-ID: <20260409131340.168556-1-pshete@nvidia.com> (raw)
From: Prathamesh Shete <pshete@nvidia.com>
Add pinctrl driver support for Tegra238 and Tegra264
along with the corresponding device tree binding
documentation. Additionally, export tegra_pinctrl_probe()
to allow the drivers to be built as loadable modules.
Prathamesh Shete (6):
pinctrl: tegra: Export tegra_pinctrl_probe()
dt-bindings: pinctrl: Document Tegra238 pin controllers
pinctrl: tegra: Add Tegra238 pinmux driver
dt-bindings: pinctrl: Document Tegra264 pin controllers
pinctrl: tegra: Add Tegra264 pinmux driver
arm64: defconfig: make Tegra 238 and Tegra264 Pinctrl a loadable
module
.../pinctrl/nvidia,tegra238-pinmux-aon.yaml | 78 +
.../nvidia,tegra238-pinmux-common.yaml | 73 +
.../pinctrl/nvidia,tegra238-pinmux.yaml | 215 ++
.../pinctrl/nvidia,tegra264-pinmux-aon.yaml | 76 +
.../nvidia,tegra264-pinmux-common.yaml | 84 +
.../pinctrl/nvidia,tegra264-pinmux-main.yaml | 163 ++
.../pinctrl/nvidia,tegra264-pinmux-uphy.yaml | 74 +
arch/arm64/configs/defconfig | 2 +
drivers/pinctrl/tegra/Kconfig | 18 +
drivers/pinctrl/tegra/Makefile | 2 +
drivers/pinctrl/tegra/pinctrl-tegra.c | 2 +
drivers/pinctrl/tegra/pinctrl-tegra238.c | 2056 +++++++++++++++
drivers/pinctrl/tegra/pinctrl-tegra264.c | 2216 +++++++++++++++++
13 files changed, 5059 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra238-pinmux-aon.yaml
create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra238-pinmux-common.yaml
create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra238-pinmux.yaml
create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra264-pinmux-aon.yaml
create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra264-pinmux-common.yaml
create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra264-pinmux-main.yaml
create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra264-pinmux-uphy.yaml
create mode 100644 drivers/pinctrl/tegra/pinctrl-tegra238.c
create mode 100644 drivers/pinctrl/tegra/pinctrl-tegra264.c
--
2.43.0
next reply other threads:[~2026-04-09 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 13:13 pshete [this message]
2026-04-09 13:13 ` [PATCH 1/6] pinctrl: tegra: Export tegra_pinctrl_probe() pshete
2026-04-09 13:13 ` [PATCH 2/6] dt-bindings: pinctrl: Document Tegra238 pin controllers pshete
2026-04-09 13:13 ` [PATCH 3/6] pinctrl: tegra: Add Tegra238 pinmux driver pshete
2026-04-09 13:13 ` [PATCH 4/6] dt-bindings: pinctrl: Document Tegra264 pin controllers pshete
2026-04-09 13:13 ` [PATCH 5/6] pinctrl: tegra: Add Tegra264 pinmux driver pshete
2026-04-09 13:13 ` [PATCH 6/6] arm64: defconfig: make Tegra238 and Tegra264 Pinctrl a loadable module pshete
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=20260409131340.168556-1-pshete@nvidia.com \
--to=pshete@nvidia.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=ebiggers@kernel.org \
--cc=geert@linux-m68k.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=michal.simek@amd.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=rosenp@gmail.com \
--cc=sven@kernel.org \
--cc=thierry.reding@kernel.org \
--cc=webgeek1234@gmail.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