Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	Brad Griffis <bgriffis@nvidia.com>, Ivy Huang <yijuh@nvidia.com>
Cc: Ninad Malwade <nmalwade@nvidia.com>, stable@vger.kernel.org
Subject: Re: [PATCH] arm64: tegra: delete the Orin NX/Nano suspend key
Date: Thu,  6 Mar 2025 19:08:06 +0100	[thread overview]
Message-ID: <174128447779.2030480.8261977491890867272.b4-ty@nvidia.com> (raw)
In-Reply-To: <20250206224034.3691397-1-yijuh@nvidia.com>

From: Thierry Reding <treding@nvidia.com>


On Thu, 06 Feb 2025 22:40:34 +0000, Ivy Huang wrote:
> As per the Orin Nano Dev Kit schematic, GPIO_G.02 is not available
> on this device family. It should not be used at all on Orin NX/Nano.
> Having this unused pin mapped as the suspend key can lead to
> unpredictable behavior for low power modes.
> 
> Orin NX/Nano uses GPIO_EE.04 as both a "power" button and a "suspend"
> button.  However, we cannot have two gpio-keys mapped to the same
> GPIO. Therefore delete the "suspend" key.
> 
> [...]

Applied, thanks!

[1/1] arm64: tegra: delete the Orin NX/Nano suspend key
      commit: c695ff32564a4e9532f2c1892ef0a7cb27cfb34c

Best regards,
-- 
Thierry Reding <treding@nvidia.com>

      reply	other threads:[~2025-03-06 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 22:40 [PATCH] arm64: tegra: delete the Orin NX/Nano suspend key Ivy Huang
2025-03-06 18:08 ` Thierry Reding [this message]

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=174128447779.2030480.8261977491890867272.b4-ty@nvidia.com \
    --to=thierry.reding@gmail.com \
    --cc=bgriffis@nvidia.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=nmalwade@nvidia.com \
    --cc=robh@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yijuh@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