From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Vidya Sagar" <vidyas@nvidia.com>,
linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Thierry Reding" <treding@nvidia.com>,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/2] PCI: {qcom-ep/tegra194}: Move endpoint cleanups to PERST# deassert handler
Date: Sat, 2 Nov 2024 22:41:07 +0530 [thread overview]
Message-ID: <20241102171107.p7j44qsi6ojokrmz@thinkpad> (raw)
In-Reply-To: <20240817-pci-qcom-ep-cleanup-v1-0-d6b958226559@linaro.org>
On Sat, Aug 17, 2024 at 11:09:02AM +0530, Manivannan Sadhasivam via B4 Relay wrote:
> Hi,
>
> This series moves the call to endpoint cleanup functions (dw_pcie_ep_cleanup()
> pci_epc_deinit_notify()) to PERST# deassert handler in qcom-ep and tegra194
> drivers. It aims to fix a crash that is seen with Qcom endpoint SoCs when host
> asserts PERST# and the cleanup functions are called without refclk.
>
> During the review of v1 [1], Bjorn suggested fixing up tegra194 driver as well
> as both drivers share the same design and require refclk from host for
> operation.
>
> Testing
> =======
>
> The Qcom patch is tested on SM8450 development board. For tegra194, I'm
> expecting someone in the Cc list or the community will do the testing.
>
> [1] https://lore.kernel.org/linux-pci/20240815224717.GA53536@bhelgaas/
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Can this series be merged for 6.13?
- Mani
> ---
> Manivannan Sadhasivam (2):
> PCI: qcom-ep: Move controller cleanups to qcom_pcie_perst_deassert()
> PCI: tegra194: Move controller cleanups to pex_ep_event_pex_rst_deassert()
>
> drivers/pci/controller/dwc/pcie-qcom-ep.c | 6 ++++--
> drivers/pci/controller/dwc/pcie-tegra194.c | 7 ++++---
> 2 files changed, 8 insertions(+), 5 deletions(-)
> ---
> base-commit: 8400291e289ee6b2bf9779ff1c83a291501f017b
> change-id: 20240817-pci-qcom-ep-cleanup-740745e21d87
>
> Best regards,
> --
> Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>
>
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2024-11-02 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 5:39 [PATCH 0/2] PCI: {qcom-ep/tegra194}: Move endpoint cleanups to PERST# deassert handler Manivannan Sadhasivam
2024-08-17 5:39 ` Manivannan Sadhasivam via B4 Relay
2024-08-17 5:39 ` [PATCH 1/2] PCI: qcom-ep: Move controller cleanups to qcom_pcie_perst_deassert() Manivannan Sadhasivam
2024-08-17 5:39 ` Manivannan Sadhasivam via B4 Relay
2024-11-03 20:53 ` Krzysztof Wilczyński
2024-08-17 5:39 ` [PATCH 2/2] PCI: tegra194: Move controller cleanups to pex_ep_event_pex_rst_deassert() Manivannan Sadhasivam
2024-08-17 5:39 ` Manivannan Sadhasivam via B4 Relay
2024-11-03 20:55 ` Krzysztof Wilczyński
2024-11-02 17:11 ` 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=20241102171107.p7j44qsi6ojokrmz@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bhelgaas@google.com \
--cc=jonathanh@nvidia.com \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.com \
--cc=vidyas@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.