From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Niklas Cassel <cassel@kernel.org>
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Damien Le Moal" <dlemoal@kernel.org>,
linux-pci@vger.kernel.org, "Bjorn Helgaas" <helgaas@kernel.org>
Subject: Re: [PATCH 1/3] PCI: dwc: ep: Add dw_pcie_ep_deinit_notify()
Date: Wed, 29 May 2024 21:10:06 +0530 [thread overview]
Message-ID: <20240529154006.GB3293@thinkpad> (raw)
In-Reply-To: <ZldBwUwyekUM-b9i@ryzen.lan>
On Wed, May 29, 2024 at 04:54:57PM +0200, Niklas Cassel wrote:
> On Wed, May 29, 2024 at 07:46:14PM +0530, Manivannan Sadhasivam wrote:
> >
> > That's fine. Thanks a lot for stepping in to fix the build issue. I was on
> > vacation, so couldn't act on your query/series promptly.
>
> Welcome back ;)
>
>
> >
> > Let us conclude the fix here itself as we have more than 1 threads going on.
> > I did consider adding the stubs to pci-epc.h, but only the deinit API requires
> > that. So I thought it will look odd to add stub for only one function, that too
> > for one of the two variants (init/deinit).
> >
> > So I went ahead with the ugly (yes) conditional for the deinit_notify API.
> >
> > Ideally, I would've expected both dwc and EP subsystem to provide stubs for the
> > APIs used by the common driver (host and EP). But since the controller drivers
> > were using the conditional check to differentiate between host and EP mode,
> > compilers were smart enough to spot the dead functions and removes them. So
> > there were no reports so far.
> >
> > But in this case, the pci_epc_deinit_notify() is called in a separate helper and
> > hence the issue.
> >
> > So to conclude, I think it is best if we can add stub just for
> > pci_epc_deinit_notify() in pci-epc.h and get rid of the dummy
> > dw_pcie_ep_init_notify() wrapper to make the init/deinit API usage consistent.
> >
> > Also I do not want to remove the wrapper for dw_pcie_ep_linkup() since its
> > conterpart dw_pcie_ep_linkdown() is required.
>
> I see, sounds good.
>
> However, if we add a stub for pci_epc_deinit_notify(), it makes sense to also
> add a stub for pci_epc_init_notify(). (I'm quite sure tegra will fail to link
> if you change it from dw_pcie_ep_init_notify() to pci_epc_init_notify()
> otherwise.)
>
No it doesn't. Reason is, the EP IRQ handler itself gets optimized out due to
the CONFIG_PCIE_TEGRA194_EP check in tegra_pcie_dw_probe().
> We should probably also address Bjorn comment:
> "ls and qcom even use *both*: pci_epc_linkdown() but dw_pcie_ep_linkup()."
>
> As far as I can tell, it is only ls (not sure why Bjorn also mentioned qcom):
> drivers/pci/controller/dwc/pci-layerscape-ep.c: pci_epc_linkdown(pci->ep.epc);
> But this should probably also be fixed to use dw_pcie_ep_linkdown().
>
Agree. I will fix that also.
- Mani
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-05-29 15:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 13:00 [PATCH 0/3] Make pci/endpoint branch build Niklas Cassel
2024-05-28 13:00 ` [PATCH 1/3] PCI: dwc: ep: Add dw_pcie_ep_deinit_notify() Niklas Cassel
2024-05-28 15:55 ` Bjorn Helgaas
2024-05-28 19:17 ` Niklas Cassel
2024-05-28 19:55 ` Bjorn Helgaas
2024-05-29 7:35 ` Niklas Cassel
2024-05-29 14:16 ` Manivannan Sadhasivam
2024-05-29 14:54 ` Niklas Cassel
2024-05-29 15:40 ` Manivannan Sadhasivam [this message]
2024-05-29 17:25 ` Bjorn Helgaas
2024-05-29 17:48 ` Niklas Cassel
2024-05-28 13:00 ` [PATCH 2/3] PCI: qcom-ep: Make use of dw_pcie_ep_deinit_notify() Niklas Cassel
2024-05-28 13:00 ` [PATCH 3/3] PCI: tegra194: " Niklas Cassel
2024-05-28 14:44 ` [PATCH 0/3] Make pci/endpoint branch build Bjorn Helgaas
2024-05-28 18:57 ` Niklas Cassel
2024-05-28 19:29 ` [PATCH 0/3] Make pci/endpoint branch buildgg Bjorn Helgaas
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=20240529154006.GB3293@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=helgaas@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@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