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>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v8 4/4] PCI: qcom: Implement shutdown() callback
Date: Mon, 9 Nov 2026 15:29:40 +0100 [thread overview]
Message-ID: <fd8b69b2-5487-4e99-a45e-d6c2ce9ae1f1@oss.qualcomm.com> (raw)
In-Reply-To: <20261107-shutdown-v8-4-bf607c6429b0@oss.qualcomm.com>
On 11/7/26 2:45 AM, Krishna Chaitanya Chundru wrote:
> From: Manivannan Sadhasivam <mani@kernel.org>
>
> PCIe host controllers should bring the link down cleanly before system
> shutdown/reboot proceeds to remove power/clocks from the controller.
> Without this, the link may still be up and endpoints still have
> transactions in flight when power/clocks are cut, which can trip SMMU
> translation faults or NoC protocol errors.
>
> Reuse dw_pcie_suspend_noirq() in the shutdown path to force the link
> into L2, putting it into D3cold.
>
> device_shutdown() runs with interrupts enabled, unlike suspend_noirq().
> Mask the chained MSI IRQ(s) and the Global IRQ before tearing down the
> link and clocks/PHY, since a late/spurious interrupt could otherwise
> reach a handler that touches now-unclocked PARF/DBI registers. Use
> dw_pcie_mask_msi() rather than dw_pcie_free_msi() so the MSI IRQ domain
> and the MSI mappings held by downstream devices (which device_shutdown()
> does not remove) are left intact.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
> ---
> drivers/pci/controller/dwc/pcie-qcom.c | 41 ++++++++++++++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
>
> diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
> index d39753f0e724..c5b06db3b92a 100644
> --- a/drivers/pci/controller/dwc/pcie-qcom.c
> +++ b/drivers/pci/controller/dwc/pcie-qcom.c
> @@ -2046,6 +2046,9 @@ static int qcom_pcie_ecam_host_init(struct pci_config_window *cfg)
>
> dw_pcie_msi_init(pp);
>
> + /* Stash pci so qcom_pcie_shutdown() can mask the MSI IRQ(s) later */
> + platform_set_drvdata(to_platform_device(dev), pci);
> +
> return devm_add_action_or_reset(dev, qcom_pci_free_msi, pp);
> }
>
> @@ -2466,6 +2469,43 @@ static int qcom_pcie_probe(struct platform_device *pdev)
> return ret;
> }
>
> +static void qcom_pcie_shutdown(struct platform_device *pdev)
> +{
> + const struct qcom_pcie_cfg *pcie_cfg = of_device_get_match_data(&pdev->dev);
> + struct qcom_pcie *pcie = NULL;
> + struct dw_pcie *pci;
> +
> + if (pcie_cfg && pcie_cfg->firmware_managed) {
> + /*
> + * Firmware owns the link teardown and clock/PHY shutdown in
> + * this mode; Linux only owns the chained MSI IRQ(s), which
> + * still need to be masked off before shutdown proceeds.
> + */
> + pci = platform_get_drvdata(pdev);
Revisiting my older comment, we can still stash `pci` in drvdata regardless
of the flavor and do `struct qcom_pcie *pcie = to_qcom_pcie(pci);` in
places where we need it
Konrad
> + } else {
> + pcie = platform_get_drvdata(pdev);
> + pci = pcie->pci;
> +
> + if (pcie->global_irq)
> + disable_irq(pcie->global_irq);
> + }
> +
> + if (pci->pp.use_imsi_rx)
> + dw_pcie_mask_msi(&pci->pp);
> +
> + /*
> + * In firmware-managed mode 'pcie' stays NULL and firmware owns the
> + * link/clock teardown. Otherwise, skip if the controller is already
> + * suspended (e.g. a prior resume failed), since dw_pcie_suspend_noirq()
> + * would touch DBI registers with clocks/interconnects already off.
> + */
> + if (pcie && !pcie->pci->suspended)
> + dw_pcie_suspend_noirq(pcie->pci, true);
> +
> + pm_runtime_put_sync(&pdev->dev);
> + pm_runtime_disable(&pdev->dev);
> +}
> +
> static int qcom_pcie_suspend_noirq(struct device *dev)
> {
> struct qcom_pcie *pcie;
> @@ -2657,5 +2697,6 @@ static struct platform_driver qcom_pcie_driver = {
> .pm = &qcom_pcie_pm_ops,
> .probe_type = PROBE_PREFER_ASYNCHRONOUS,
> },
> + .shutdown = qcom_pcie_shutdown,
> };
> builtin_platform_driver(qcom_pcie_driver);
>
prev parent reply other threads:[~2026-11-09 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 1:45 [PATCH v8 0/4] PCI: qcom: Implement shutdown() to avoid SMMU/NoC errors on reboot Krishna Chaitanya Chundru
2026-11-07 1:45 ` [PATCH v8 1/4] PCI: host-common: Fix early bus-walk exit in d3cold_possible() Krishna Chaitanya Chundru
2026-11-07 1:45 ` [PATCH v8 2/4] PCI: dwc: Force L2 link entry on shutdown/reboot without D3cold check Krishna Chaitanya Chundru
2026-11-07 1:45 ` [PATCH v8 3/4] PCI: dwc: Add dw_pcie_mask_msi() to mask chained MSI without freeing domain Krishna Chaitanya Chundru
2026-11-07 1:45 ` [PATCH v8 4/4] PCI: qcom: Implement shutdown() callback Krishna Chaitanya Chundru
2026-11-09 14:29 ` Konrad Dybcio [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=fd8b69b2-5487-4e99-a45e-d6c2ce9ae1f1@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=krishna.chundru@oss.qualcomm.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=mani@kernel.org \
--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 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®