From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: "Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Will Deacon" <will@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jonathanh@nvidia.com,
bjorn.andersson@oss.qualcomm.com
Subject: Re: [PATCH v3 5/5] PCI: qcom: Add D3cold support
Date: Tue, 17 Mar 2026 10:15:41 +0100 [thread overview]
Message-ID: <f3344006-5511-4f1b-aea3-7dc81a091cd8@oss.qualcomm.com> (raw)
In-Reply-To: <20260311-d3cold-v3-5-4d85dc7c2695@oss.qualcomm.com>
On 3/11/26 11:26 AM, Krishna Chaitanya Chundru wrote:
> Add support for transitioning PCIe endpoints & bridges into D3cold by
> integrating with the DWC core suspend/resume helpers.
>
> Implement PME_TurnOff message generation via ELBI_SYS_CTRL and hook it
> into the DWC host operations so the controller follows the standard
> PME_TurnOff-based power-down sequence before entering D3cold.
>
> When the device is suspended into D3cold, fully tear down interconnect
> bandwidth, OPP votes. If D3cold is not entered, retain existing behavior
> by keeping the required interconnect and OPP votes.
>
> Drop the qcom_pcie::suspended flag and rely on the existing
> dw_pcie::suspended state, which now drives both the power-management
> flow and the interconnect/OPP handling.
>
> Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
> ---
[...]
> ret = icc_disable(pcie->icc_cpu);
> if (ret)
> dev_err(dev, "Failed to disable CPU-PCIe interconnect path: %d\n", ret);
>
> if (pcie->use_pm_opp)
> dev_pm_opp_set_opp(pcie->pci->dev, NULL);
Does calling .suspend not drop the vote by itself?
[...]
> @@ -2132,25 +2138,46 @@ static int qcom_pcie_resume_noirq(struct device *dev)
Similarly, I'd expect that .resume restores it (and you didn't do it manually)
Konrad
next prev parent reply other threads:[~2026-03-17 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 10:26 [PATCH v3 0/5] " Krishna Chaitanya Chundru
2026-03-11 10:26 ` [PATCH v3 1/5] PCI: host-common: Add helper to determine host bridge D3cold eligibility Krishna Chaitanya Chundru
2026-03-16 5:17 ` Manivannan Sadhasivam
2026-03-11 10:26 ` [PATCH v3 2/5] PCI: dwc: Use common D3cold eligibility helper in suspend path Krishna Chaitanya Chundru
2026-03-11 10:26 ` [PATCH v3 3/5] PCI: qcom: Add .get_ltssm() helper Krishna Chaitanya Chundru
2026-03-11 10:26 ` [PATCH v3 4/5] PCI: qcom: Power down PHY via PARF_PHY_CTRL before disabling rails/clocks Krishna Chaitanya Chundru
2026-03-11 10:26 ` [PATCH v3 5/5] PCI: qcom: Add D3cold support Krishna Chaitanya Chundru
2026-03-17 9:15 ` Konrad Dybcio [this message]
2026-04-06 9:08 ` Krishna Chaitanya Chundru
2026-04-07 11:36 ` Konrad Dybcio
2026-04-07 11:37 ` Krishna Chaitanya Chundru
2026-04-07 12:27 ` Konrad Dybcio
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=f3344006-5511-4f1b-aea3-7dc81a091cd8@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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=mani@kernel.org \
--cc=robh@kernel.org \
--cc=will@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 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®