From: Thierry Reding <thierry.reding@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thierry Reding <treding@nvidia.com>
Subject: [PATCH 0/2] arm64: tegra: Add gpio-keys for Jetson AGX Thor DevKit
Date: Thu, 27 Aug 2026 16:54:17 +0200 [thread overview]
Message-ID: <20260827-tegra264-gpio-keys-v1-0-89518c5fb29f@nvidia.com> (raw)
This set of patches cleans up some existing gpio-keys DT nodes and adds
support for the power and force-recovery keys on Jetson AGX Thor.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
Thierry Reding (2):
arm64: tegra: Use consistent key code for force-recovery button
arm64: tegra: Enable GPIO keys on Jetson AGX Thor
arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 2 +-
.../boot/dts/nvidia/tegra234-p3737-0000+p3701.dtsi | 9 +--------
.../dts/nvidia/tegra234-p3740-0002+p3701-0008.dts | 9 +--------
.../boot/dts/nvidia/tegra234-p3768-0000+p3767.dtsi | 2 +-
.../boot/dts/nvidia/tegra264-p4071-0000+p3834.dtsi | 23 ++++++++++++++++++++++
arch/arm64/boot/dts/nvidia/tegra264.dtsi | 1 +
6 files changed, 28 insertions(+), 18 deletions(-)
---
base-commit: 6a746cd265aed59107ebdaa9ce039bb832922969
change-id: 20260817-tegra264-gpio-keys-95479ebd99fc
Best regards,
--
Thierry Reding <treding@nvidia.com>
next reply other threads:[~2026-08-27 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 14:54 Thierry Reding [this message]
2026-08-27 14:54 ` [PATCH 1/2] arm64: tegra: Use consistent key code for force-recovery button Thierry Reding
2026-08-27 14:54 ` [PATCH 2/2] arm64: tegra: Enable GPIO keys on Jetson AGX Thor Thierry Reding
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=20260827-tegra264-gpio-keys-v1-0-89518c5fb29f@nvidia.com \
--to=thierry.reding@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@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