From: Thierry Reding <thierry.reding@kernel.org>
To: Manikanta Maddireddy <mmaddireddy@nvidia.com>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
Prathamesh Shete <pshete@nvidia.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Enable PCIe WAKE# as a system wake source on Tegra234
Date: Fri, 2 Oct 2026 10:21:30 +0200 [thread overview]
Message-ID: <ar9pfNZstgn9pPXK@orome> (raw)
In-Reply-To: <20260907113134.2543273-1-mmaddireddy@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 2546 bytes --]
On Mon, Sep 07, 2026 at 05:01:32PM +0530, Manikanta Maddireddy wrote:
> The P3768 carrier board used by Jetson Orin NX and Orin Nano routes the
> PCIe WAKE# signal to Tegra234 main GPIO L.2. Nothing in the kernel
> currently describes that signal, so a suspended system cannot be woken
> by a PCIe endpoint.
>
> This series wires it up in two steps.
>
> Patch 1 adds the PMC wake event mapping for GPIO L.2. This is the piece
> that lets the GPIO interrupt be armed as a system wake source during
> suspend, rather than being treated as an ordinary interrupt that is
> masked along with the rest of the GPIO controller.
>
> Patch 2 describes the signal in device tree, on the root port of the C8
> controller. C8 is the controller with the onboard Ethernet NIC on this
> carrier, so describing WAKE# there is what makes wake-on-LAN usable.
> The property is consumed by the generic PCI core in
> pci_configure_of_wake_gpio(), which looks it up on the OF node of the
> PCI device itself, so no controller driver change is needed.
>
> The two patches touch different subsystems but are only useful together,
> so they are posted as one series. Patch 2 depends on patch 1 to have any
> effect.
>
> Testing:
>
> - Verification:
> - Verified suspend-to-RAM functionality with no spurious pending
> wake sources observed.
> - Verified wake up through GPIO L.2 using an Ethernet magic packet.
> - Verified the reported wake source after resume.
> - Verified that regular Ethernet traffic does not trigger an
> unintended wake-up.
> - Confirmed Ethernet connectivity and normal network operation
> after resume.
> - Repeated multiple suspend/resume cycles to verify consistent
> behavior.
> - make ARCH=arm64 CHECK_DTBS=y is clean for the two affected boards,
> tegra234-p3768-0000+p3767-0000 and -0005, with dtschema 2026.6.
> - checkpatch --strict reports no issues on either patch.
>
> Note: the series is based on the linux-next 20260817 snapshot rather
> than a maintainer tree; see the base-commit trailer below. Happy to
> rebase onto whichever tree you prefer.
>
> Manikanta Maddireddy (2):
> soc/tegra: pmc: Add PCIe wake event for Tegra234
> arm64: tegra: Add PCIe wake GPIO for Jetson Orin NX/Nano
>
> .../boot/dts/nvidia/tegra234-p3768-0000+p3767.dtsi | 10 ++++++++++
> drivers/soc/tegra/pmc.c | 1 +
> 2 files changed, 11 insertions(+)
Both patches applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-10-02 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 11:31 [PATCH v1 0/2] Enable PCIe WAKE# as a system wake source on Tegra234 Manikanta Maddireddy
2026-09-07 11:31 ` [PATCH v1 1/2] soc/tegra: pmc: Add PCIe wake event for Tegra234 Manikanta Maddireddy
2026-09-07 11:31 ` [PATCH v1 2/2] arm64: tegra: Add PCIe wake GPIO for Jetson Orin NX/Nano Manikanta Maddireddy
2026-10-02 8:21 ` 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=ar9pfNZstgn9pPXK@orome \
--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=mmaddireddy@nvidia.com \
--cc=pshete@nvidia.com \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.