From: Bjorn Helgaas <helgaas@kernel.org>
To: Manikanta Maddireddy <mmaddireddy@nvidia.com>
Cc: bhelgaas@google.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
thierry.reding@gmail.com, jonathanh@nvidia.com,
kishon@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org,
Frank.Li@nxp.com, den@valinux.co.jp, hongxing.zhu@nxp.com,
jingoohan1@gmail.com, vidyas@nvidia.com, cassel@kernel.org,
18255117159@163.com, linux-pci@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 09/13] PCI: tegra194: Allow system suspend when the Endpoint link is not up
Date: Mon, 2 Mar 2026 17:30:55 -0600 [thread overview]
Message-ID: <20260302233055.GA4036827@bhelgaas> (raw)
In-Reply-To: <20260223184151.3083221-10-mmaddireddy@nvidia.com>
On Tue, Feb 24, 2026 at 12:11:47AM +0530, Manikanta Maddireddy wrote:
> From: Vidya Sagar <vidyas@nvidia.com>
>
> Only a Root port initiates the L2 sequence. PCIe link is kept in L2 state
> during suspend. If Endpoint mode is enabled and the link is up, the
> software cannot proceed with suspend. However, when the PCIe Endpoint
> driver is probed, but the PCIe link is not up, Tegra can go into suspend
> state. So, allow system to suspend in this case.
Would be nice to consistently use "Root Port" throughout the series
instead of the current mix of "root port", "Root port", "Root Port".
Using "Endpoint" is also nice because these are proper nouns defined
by the PCIe spec.
next prev parent reply other threads:[~2026-03-02 23:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 18:41 [PATCH v6 00/13] Fixes to pcie-tegra194 driver Manikanta Maddireddy
2026-02-23 18:41 ` [PATCH v6 01/13] PCI: tegra194: Fix polling delay for L2 state Manikanta Maddireddy
2026-02-27 12:32 ` Vidya Sagar
2026-03-02 23:17 ` Bjorn Helgaas
2026-02-23 18:41 ` [PATCH v6 02/13] PCI: tegra194: Refactor LTSSM state polling on surprise down Manikanta Maddireddy
2026-02-27 12:32 ` Vidya Sagar
2026-02-23 18:41 ` [PATCH v6 03/13] PCI: tegra194: Don't force the device into the D0 state before L2 Manikanta Maddireddy
2026-02-27 12:33 ` Vidya Sagar
2026-02-23 18:41 ` [PATCH v6 04/13] PCI: tegra194: Disable PERST IRQ only in Endpoint mode Manikanta Maddireddy
2026-02-27 12:33 ` Vidya Sagar
2026-02-23 18:41 ` [PATCH v6 05/13] PCI: tegra194: Use devm_gpiod_get_optional() to parse "nvidia,refclk-select" Manikanta Maddireddy
2026-02-27 12:33 ` Vidya Sagar
2026-02-23 18:41 ` [PATCH v6 06/13] PCI: tegra194: Disable direct speed change for EP Manikanta Maddireddy
2026-02-27 12:33 ` Vidya Sagar
2026-02-23 18:41 ` [PATCH v6 07/13] PCI: tegra194: Set LTR message request before PCIe link up Manikanta Maddireddy
2026-02-27 12:33 ` Vidya Sagar
2026-03-02 23:27 ` Bjorn Helgaas
2026-02-23 18:41 ` [PATCH v6 08/13] PCI: tegra194: Apply pinctrl settings for both PCIe RP and EP Manikanta Maddireddy
2026-02-27 12:34 ` Vidya Sagar
2026-02-23 18:41 ` [PATCH v6 09/13] PCI: tegra194: Allow system suspend when the Endpoint link is not up Manikanta Maddireddy
2026-02-27 12:34 ` Vidya Sagar
2026-03-02 23:30 ` Bjorn Helgaas [this message]
2026-02-23 18:41 ` [PATCH v6 10/13] PCI: tegra194: Free up EP resources during remove() Manikanta Maddireddy
2026-02-27 12:34 ` Vidya Sagar
2026-02-23 18:41 ` [PATCH v6 11/13] PCI: tegra194: Use HW version number Manikanta Maddireddy
2026-02-27 12:34 ` Vidya Sagar
2026-02-23 18:41 ` [PATCH v6 12/13] PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on Manikanta Maddireddy
2026-02-27 12:34 ` Vidya Sagar
2026-02-23 18:41 ` [PATCH v6 13/13] PCI: tegra194: Free resources during controller deinitialization Manikanta Maddireddy
2026-02-27 12:34 ` Vidya Sagar
2026-02-27 16:59 ` [PATCH v6 00/13] Fixes to pcie-tegra194 driver Jon Hunter
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=20260302233055.GA4036827@bhelgaas \
--to=helgaas@kernel.org \
--cc=18255117159@163.com \
--cc=Frank.Li@nxp.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=conor+dt@kernel.org \
--cc=den@valinux.co.jp \
--cc=gregkh@linuxfoundation.org \
--cc=hongxing.zhu@nxp.com \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mmaddireddy@nvidia.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vidyas@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