From: Marc Zyngier <maz@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: "Frank Li" <Frank.Li@nxp.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Richard Zhu" <hongxing.zhu@nxp.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
alyssa@rosenzweig.io, bpf@vger.kernel.org, broonie@kernel.org,
jgg@ziepe.ca, joro@8bytes.org, lgirdwood@gmail.com,
p.zabel@pengutronix.de, robin.murphy@arm.com, will@kernel.org
Subject: Re: [PATCH v3 1/2] PCI: Add enable_device() and disable_device() callbacks for bridges
Date: Sat, 02 Nov 2024 11:32:37 +0000 [thread overview]
Message-ID: <86jzdl27my.wl-maz@kernel.org> (raw)
In-Reply-To: <20241102111012.23zwz4et2qkafyca@thinkpad>
On Sat, 02 Nov 2024 11:10:12 +0000,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> wrote:
>
> On Thu, Oct 24, 2024 at 06:34:44PM -0400, Frank Li wrote:
> > Some PCIe host bridges require special handling when enabling or disabling
> > PCIe Endpoints. For example, the i.MX95 platform has a lookup table to map
> > Requester IDs to StreamIDs, which are used by the SMMU and MSI controller
> > to identify the source of DMA accesses.
> >
> > Without this mapping, DMA accesses may target unintended memory, which
> > would corrupt memory or read the wrong data.
> >
> > Add a host bridge .enable_device() hook the imx6 driver can use to
> > configure the Requester ID to StreamID mapping. The hardware table isn't
> > big enough to map all possible Requester IDs, so this hook may fail if no
> > table space is available. In that case, return failure from
> > pci_enable_device().
> >
> > It might make more sense to make pci_set_master() decline to enable bus
> > mastering and return failure, but it currently doesn't have a way to return
> > failure.
> >
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
> > Change from v2 to v3
> > - use Bjorn suggest's commit message.
> > - call disable_device() when error happen.
> >
> > Change from v1 to v2
> > - move enable(disable)device ops to pci_host_bridge
> > ---
> > drivers/pci/pci.c | 23 ++++++++++++++++++++++-
> > include/linux/pci.h | 2 ++
> > 2 files changed, 24 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> > index 7d85c04fbba2a..5e0cb9b6f4d4f 100644
> > --- a/drivers/pci/pci.c
> > +++ b/drivers/pci/pci.c
> > @@ -2056,6 +2056,7 @@ int __weak pcibios_enable_device(struct pci_dev *dev, int bars)
> > static int do_pci_enable_device(struct pci_dev *dev, int bars)
> > {
> > int err;
> > + struct pci_host_bridge *host_bridge;
> > struct pci_dev *bridge;
> > u16 cmd;
> > u8 pin;
> > @@ -2068,9 +2069,16 @@ static int do_pci_enable_device(struct pci_dev *dev, int bars)
> > if (bridge)
> > pcie_aspm_powersave_config_link(bridge);
> >
> > + host_bridge = pci_find_host_bridge(dev->bus);
> > + if (host_bridge && host_bridge->enable_device) {
> > + err = host_bridge->enable_device(host_bridge, dev);
> > + if (err)
> > + return err;
> > + }
>
> How about wrapping the enable/disable part in a helper?
>
> int pci_host_bridge_enable_device(dev);
> void pci_host_bridge_disable_device(dev);
>
> The definition could be placed in drivers/pci/pci.h as an inline
> function.
What does it bring? I would see the point if there was another user.
But this is very much core infrastructure which doesn't lend itself to
duplication.
Unless you have something in mind?
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-11-02 11:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 22:34 [PATCH v3 0/2] PCI: add enabe(disable)_device() hook for bridge Frank Li
2024-10-24 22:34 ` [PATCH v3 1/2] PCI: Add enable_device() and disable_device() callbacks for bridges Frank Li
2024-10-30 21:00 ` Bjorn Helgaas
2024-11-01 16:58 ` Marc Zyngier
2024-11-02 11:10 ` Manivannan Sadhasivam
2024-11-02 11:32 ` Marc Zyngier [this message]
2024-11-02 11:54 ` Manivannan Sadhasivam
2024-11-02 12:24 ` Marc Zyngier
2024-11-02 12:48 ` Manivannan Sadhasivam
2024-10-24 22:34 ` [PATCH v3 2/2] PCI: imx6: Add IOMMU and ITS MSI support for i.MX95 Frank Li
2024-11-01 17:23 ` Robin Murphy
2024-11-02 11:49 ` Manivannan Sadhasivam
2024-11-02 17:26 ` Frank Li
2024-11-02 22:18 ` Marc Zyngier
2024-11-03 6:23 ` Manivannan Sadhasivam
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=86jzdl27my.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alyssa@rosenzweig.io \
--cc=bhelgaas@google.com \
--cc=bpf@vger.kernel.org \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kernel@pengutronix.de \
--cc=kw@linux.com \
--cc=l.stach@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).