From: Jon Hunter <jonathanh@nvidia.com>
To: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>
Cc: Thierry Reding <treding@nvidia.com>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
<linux-kernel@vger.kernel.org>, Jon Hunter <jonathanh@nvidia.com>
Subject: [PATCH 0/2] gpio: tegra186: Add support for Tegra268
Date: Fri, 28 Aug 2026 15:39:50 +0100 [thread overview]
Message-ID: <20260828-tegra-tegra268-gpio-v1-0-317bd91295e2@nvidia.com> (raw)
Add support for the GPIO controllers on the Tegra268 device. At the
moment there is no device-tree platform/board supported in the mainline
kernel for Tegra268, but we will be working to add this. For now we are
starting to upstream some basic driver support to pave the way for
supporting Tegra268 based platforms.
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
---
Jon Hunter (2):
dt-bindings: gpio: Add compatible string for Tegra268
gpio: tegra186: Add support for Tegra268
.../bindings/gpio/nvidia,tegra186-gpio.yaml | 9 +++
drivers/gpio/gpio-tegra186.c | 74 ++++++++++++++++++++++
2 files changed, 83 insertions(+)
---
base-commit: 3d83758432b5e6ed9507500a57efb0f3af41ee7d
change-id: 20260828-tegra-tegra268-gpio-e77cbf459696
Best regards,
--
Jon Hunter <jonathanh@nvidia.com>
next reply other threads:[~2026-08-28 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 14:39 Jon Hunter [this message]
2026-08-28 14:39 ` [PATCH 1/2] dt-bindings: gpio: Add compatible string for Tegra268 Jon Hunter
2026-08-28 16:22 ` Conor Dooley
2026-08-28 14:39 ` [PATCH 2/2] gpio: tegra186: Add support " Jon Hunter
2026-08-28 14:56 ` sashiko-bot
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=20260828-tegra-tegra268-gpio-v1-0-317bd91295e2@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=thierry.reding@kernel.org \
--cc=treding@nvidia.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