From: Bjorn Helgaas <helgaas@kernel.org> To: Jisheng Zhang <Jisheng.Zhang@synaptics.com> Cc: Jingoo Han <jingoohan1@gmail.com>, Gustavo Pimentel <gustavo.pimentel@synopsys.com>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, Rob Herring <robh@kernel.org>, Bjorn Helgaas <bhelgaas@google.com>, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Kishon Vijay Abraham I <kishon@ti.com>, Richard Zhu <hongxing.zhu@nxp.com>, Lucas Stach <l.stach@pengutronix.de>, Dilip Kota <eswara.kota@linux.intel.com> Subject: Re: [PATCH RESEND] PCI: dwc: Fix MSI not work after resume Date: Mon, 22 Mar 2021 20:24:41 -0500 [thread overview] Message-ID: <20210323012441.GA515937@bjorn-Precision-5520> (raw) In-Reply-To: <20210301111031.220a38b8@xhacker.debian> [+cc Kishon, Richard, Lucas, Dilip] On Mon, Mar 01, 2021 at 11:10:31AM +0800, Jisheng Zhang wrote: > After we move dw_pcie_msi_init() into core -- dw_pcie_host_init(), the > MSI stops working after resume. Because dw_pcie_host_init() is only > called once during probe. To fix this issue, we move dw_pcie_msi_init() > to dw_pcie_setup_rc(). This patch looks fine, but I don't think the commit log tells the whole story. Prior to 59fbab1ae40e, it looks like the only dwc-based drivers with resume functions were dra7xx, imx6, intel-gw, and tegra [1]. Only tegra called dw_pcie_msi_init() in the resume path, and I do think 59fbab1ae40e broke MSI after resume because it removed the dw_pcie_msi_init() call from tegra_pcie_enable_msi_interrupts(). I'm not convinced this patch fixes it reliably, though. The call chain looks like this: tegra_pcie_dw_resume_noirq tegra_pcie_dw_start_link if (dw_pcie_wait_for_link(pci)) dw_pcie_setup_rc dw_pcie_wait_for_link() returns 0 if the link is up, so we only call dw_pcie_setup_rc() in the case where the link *didn't* come up. If the link comes up nicely without retry, we won't call dw_pcie_setup_rc() and hence won't call dw_pcie_msi_init(). Since then, exynos added a resume function. My guess is MSI never worked after resume for dra7xx, exynos, imx6, and intel-gw because they don't call dw_pcie_msi_init() in their resume functions. This patch looks like it should fix MSI after resume for exynos, imx6, and intel-gw because they *do* call dw_pcie_setup_rc() from their resume functions [2], and after this patch, dw_pcie_msi_init() will be called from there. I suspect MSI after resume still doesn't work on dra7xx. [1] git grep -A20 -e "static.*resume_noirq" 59fbab1ae40e^:drivers/pci/controller/dwc [2] git grep -A20 -e "static.*resume_noirq" drivers/pci/controller/dwc > Fixes: 59fbab1ae40e ("PCI: dwc: Move dw_pcie_msi_init() into core") > Reviewed-by: Rob Herring <robh@kernel.org> > Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com> > --- > Since v1: > - collect Reviewed-by tag > > drivers/pci/controller/dwc/pcie-designware-host.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c b/drivers/pci/controller/dwc/pcie-designware-host.c > index 7e55b2b66182..e6c274f4485c 100644 > --- a/drivers/pci/controller/dwc/pcie-designware-host.c > +++ b/drivers/pci/controller/dwc/pcie-designware-host.c > @@ -400,7 +400,6 @@ int dw_pcie_host_init(struct pcie_port *pp) > } > > dw_pcie_setup_rc(pp); > - dw_pcie_msi_init(pp); > > if (!dw_pcie_link_up(pci) && pci->ops && pci->ops->start_link) { > ret = pci->ops->start_link(pci); > @@ -551,6 +550,8 @@ void dw_pcie_setup_rc(struct pcie_port *pp) > } > } > > + dw_pcie_msi_init(pp); > + > /* Setup RC BARs */ > dw_pcie_writel_dbi(pci, PCI_BASE_ADDRESS_0, 0x00000004); > dw_pcie_writel_dbi(pci, PCI_BASE_ADDRESS_1, 0x00000000); > -- > 2.30.1 >
next prev parent reply other threads:[~2021-03-23 1:25 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-01 3:10 Jisheng Zhang 2021-03-18 18:23 ` Bjorn Helgaas 2021-03-23 1:24 ` Bjorn Helgaas [this message] 2021-03-23 3:01 ` Jisheng Zhang 2021-03-23 15:12 ` Bjorn Helgaas 2021-03-23 16:04 ` Kishon Vijay Abraham I
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=20210323012441.GA515937@bjorn-Precision-5520 \ --to=helgaas@kernel.org \ --cc=Jisheng.Zhang@synaptics.com \ --cc=bhelgaas@google.com \ --cc=eswara.kota@linux.intel.com \ --cc=gustavo.pimentel@synopsys.com \ --cc=hongxing.zhu@nxp.com \ --cc=jingoohan1@gmail.com \ --cc=kishon@ti.com \ --cc=l.stach@pengutronix.de \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=robh@kernel.org \ --subject='Re: [PATCH RESEND] PCI: dwc: Fix MSI not work after resume' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).