From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
To: "Jingoo Han" <jingoohan1@gmail.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@oss.qualcomm.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
vincent.guittot@linaro.org, zhangsenchuan@eswincomputing.com,
Frank Li <Frank.Li@nxp.com>, Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: (subset) [PATCH v2 0/2] PCI: dwc: Suspend/resume rework
Date: Thu, 18 Dec 2025 18:39:44 +0530 [thread overview]
Message-ID: <176606338499.520109.15893427341689041404.b4-ty@kernel.org> (raw)
In-Reply-To: <20251218-pci-dwc-suspend-rework-v2-0-5a7778c6094a@oss.qualcomm.com>
On Thu, 18 Dec 2025 17:34:51 +0530, Manivannan Sadhasivam wrote:
> This series is a rework of [1] to allow DWC vendor glue drivers to use the
> dw_pcie_suspend_noirq() and dw_pcie_resume_noirq() APIs without failures as
> reported in [2][3].
>
> Currently, both of these APIs will fail if there is no device connected to the
> bus. This is not fair as suspend/resume should continue even if there is no
> device. Hence, this series tries to address this limitation.
>
> [...]
Applied, thanks!
[1/2] PCI: dwc: Skip PME_Turn_Off broadcast and L2/L3 transition during suspend if link is not up
commit: c4a86e6600fa082d6646044fcce2183ad5e52283
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
prev parent reply other threads:[~2025-12-18 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 12:04 [PATCH v2 0/2] PCI: dwc: Suspend/resume rework Manivannan Sadhasivam via B4 Relay
2025-12-18 12:04 ` [PATCH v2 1/2] PCI: dwc: Skip PME_Turn_Off broadcast and L2/L3 transition during suspend if link is not up Manivannan Sadhasivam via B4 Relay
2025-12-18 12:04 ` [PATCH v2 2/2] PCI: dwc: Do not return failure if link is in Detect.Quiet/Active states Manivannan Sadhasivam via B4 Relay
2025-12-18 12:27 ` Krishna Chaitanya Chundru
2025-12-18 12:46 ` Manivannan Sadhasivam
2025-12-18 12:56 ` Krishna Chaitanya Chundru
2025-12-18 13:00 ` Manivannan Sadhasivam
2025-12-18 13:28 ` Krishna Chaitanya Chundru
2025-12-18 12:45 ` Shawn Lin
2025-12-18 12:55 ` Manivannan Sadhasivam
2025-12-18 13:09 ` Manivannan Sadhasivam [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=176606338499.520109.15893427341689041404.b4-ty@kernel.org \
--to=manivannan.sadhasivam@oss.qualcomm.com \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=vincent.guittot@linaro.org \
--cc=zhangsenchuan@eswincomputing.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