From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
To: lpieralisi@kernel.org, kwilczynski@kernel.org,
bhelgaas@google.com,
Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Cc: will@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
linux-arm-msm@vger.kernel.org, zhangsenchuan@eswincomputing.com,
vincent.guittot@linaro.org
Subject: Re: [PATCH v2 0/3] PCI: dwc: Check for device presence in suspend and resume
Date: Sat, 08 Nov 2025 15:54:12 +0530 [thread overview]
Message-ID: <176259745262.10508.495485306102349892.b4-ty@kernel.org> (raw)
In-Reply-To: <20251107044319.8356-1-manivannan.sadhasivam@oss.qualcomm.com>
On Fri, 07 Nov 2025 10:13:16 +0530, Manivannan Sadhasivam wrote:
> This series aims to fix the usage of dw_pcie_link_up() API to check for Link up
> during system suspend. The motivation for this series comes from recent
> discussions [1] [2], where developers wanted to skip PME_Turn_Off broadcast in
> dw_pcie_suspend_noirq() API when devices are not attached to the bus. They ended
> up using dw_pcie_link_up() to check for the device presence due to the bad
> example in the pcie-qcom driver which does the same. The usage of
> dw_pcie_link_up() API here would be racy as the link can go down at any time
> after the check.
>
> [...]
Applied, thanks!
[1/3] PCI: host-common: Add an API to check for any device under the Root Ports
commit: 64a4b36d229120a71ede91aed16519164a181c13
[2/3] PCI: qcom: Check for the presence of a device instead of Link up during suspend
commit: b6811cd64ac54fb2426b6ce35ba7c63588402687
[3/3] PCI: dwc: Check for the device presence during suspend and resume
commit: e8fe6b3413a1b92b4bc0f0182ea4b49ee369541b
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
next prev parent reply other threads:[~2025-11-08 10:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 4:43 Manivannan Sadhasivam
2025-11-07 4:43 ` [PATCH v2 1/3] PCI: host-common: Add an API to check for any device under the Root Ports Manivannan Sadhasivam
2025-11-10 16:36 ` Frank Li
2025-11-07 4:43 ` [PATCH v2 2/3] PCI: qcom: Check for the presence of a device instead of Link up during suspend Manivannan Sadhasivam
2025-11-13 16:41 ` Bjorn Helgaas
2025-11-13 16:54 ` Manivannan Sadhasivam
2025-11-13 17:22 ` Bjorn Helgaas
2025-11-17 17:37 ` Manivannan Sadhasivam
2025-11-19 8:03 ` zhangsenchuan
2025-11-19 16:15 ` Manivannan Sadhasivam
2025-11-07 4:43 ` [PATCH v2 3/3] PCI: dwc: Check for the device presence during suspend and resume Manivannan Sadhasivam
2025-11-10 16:26 ` Frank Li
2025-11-13 16:56 ` Manivannan Sadhasivam
2025-11-13 16:40 ` Bjorn Helgaas
2025-11-13 17:01 ` Manivannan Sadhasivam
2025-11-14 2:03 ` zhangsenchuan
2025-11-08 10:24 ` Manivannan Sadhasivam [this message]
2025-11-10 10:48 ` [PATCH v2 0/3] PCI: dwc: Check for device presence in " Vincent Guittot
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=176259745262.10508.495485306102349892.b4-ty@kernel.org \
--to=manivannan.sadhasivam@oss.qualcomm.com \
--cc=bhelgaas@google.com \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®