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 v5 3/3] PCI: qcom: Implement shutdown() callback
Date: Wed, 9 Sep 2026 12:56:05 +0200 [thread overview]
Message-ID: <ca45caec-01a8-438d-a91b-98a2ef411576@oss.qualcomm.com> (raw)
In-Reply-To: <20260905-shutdown-v5-3-f0c6bafa1d4f@oss.qualcomm.com>
On 9/5/26 2:48 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.
[...]
> +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;
> +
> + 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.
> + */
> + struct dw_pcie *pci = platform_get_drvdata(pdev);
> +
> + if (pci->pp.use_imsi_rx)
> + dw_pcie_free_msi(&pci->pp);
> + return;
> + }
> +
> + pcie = platform_get_drvdata(pdev);
> + if (pcie) {
> + if (pcie->pci->pp.use_imsi_rx)
> + dw_pcie_free_msi(&pcie->pci->pp);
> +
> + if (pcie->global_irq)
> + disable_irq(pcie->global_irq);
> +
> + pcie->pci->pp.force_d3cold = true;
> + dw_pcie_suspend_noirq(pcie->pci);
> + }
> +
if (!pcie)
return/warn (should it be possible?)
if (pci->pp.use_imsi_rx)
dw_pcie_free_msi(&pci->pp);
/* abc xyz */
if (firwmare_managed)
return;
will save you indentation and de-duplicate the free_msi() call
Konrad
next prev parent reply other threads:[~2026-09-09 10:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 0:48 [PATCH v5 0/3] PCI: qcom: Implement shutdown() to avoid SMMU/NoC errors on reboot Krishna Chaitanya Chundru
2026-09-05 0:48 ` [PATCH v5 1/3] PCI: host-common: Fix early bus-walk exit in d3cold_possible() Krishna Chaitanya Chundru
2026-09-05 0:56 ` sashiko-bot
2026-09-09 10:50 ` Konrad Dybcio
2026-09-05 0:48 ` [PATCH v5 2/3] PCI: dwc: Force L2 link entry on shutdown/reboot without D3cold check Krishna Chaitanya Chundru
2026-09-05 1:01 ` sashiko-bot
2026-09-09 10:53 ` Konrad Dybcio
2026-09-09 11:00 ` Manivannan Sadhasivam
2026-09-09 11:47 ` Krishna Chaitanya Chundru
2026-09-05 0:48 ` [PATCH v5 3/3] PCI: qcom: Implement shutdown() callback Krishna Chaitanya Chundru
2026-09-05 1:03 ` sashiko-bot
2026-09-09 10:56 ` Konrad Dybcio [this message]
2026-09-09 11:49 ` Krishna Chaitanya Chundru
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=ca45caec-01a8-438d-a91b-98a2ef411576@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