From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: kw@linux.com, kishon@kernel.org, bhelgaas@google.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, dlemoal@kernel.org
Subject: Re: [PATCH v6 2/9] PCI: endpoint: Pass EPF device ID to the probe function
Date: Mon, 5 Jun 2023 15:06:57 +0200 [thread overview]
Message-ID: <ZH3d8S1V3u8ppM62@lpieralisi> (raw)
In-Reply-To: <20230605115746.GD5536@thinkpad>
On Mon, Jun 05, 2023 at 05:27:46PM +0530, Manivannan Sadhasivam wrote:
> On Mon, Jun 05, 2023 at 11:27:09AM +0200, Lorenzo Pieralisi wrote:
> > On Fri, Jun 02, 2023 at 05:17:49PM +0530, Manivannan Sadhasivam wrote:
> > > Currently, the EPF probe function doesn't get the device ID argument needed
> > > to correctly identify the device table ID of the EPF device.
> > >
> > > When multiple entries are added to the "struct pci_epf_device_id" table,
> > > the probe function needs to identify the correct one. This is achieved by
> > > modifying the pci_epf_match_id() function to return the match ID pointer
> > > and passing it to the driver's probe function.
> > >
> > > pci_epf_device_match() function can return bool based on the return value
> > > of pci_epf_match_id().
> > >
> > > Reviewed-by: Kishon Vijay Abraham I <kishon@kernel.org>
> > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > > ---
> > > drivers/pci/endpoint/functions/pci-epf-ntb.c | 3 ++-
> > > drivers/pci/endpoint/functions/pci-epf-test.c | 2 +-
> > > drivers/pci/endpoint/functions/pci-epf-vntb.c | 2 +-
> > > drivers/pci/endpoint/pci-epf-core.c | 18 +++++++++++-------
> > > include/linux/pci-epf.h | 4 +++-
> > > 5 files changed, 18 insertions(+), 11 deletions(-)
> > >
> > > diff --git a/drivers/pci/endpoint/functions/pci-epf-ntb.c b/drivers/pci/endpoint/functions/pci-epf-ntb.c
> > > index 9a00448c7e61..980b4ecf19a2 100644
> > > --- a/drivers/pci/endpoint/functions/pci-epf-ntb.c
> > > +++ b/drivers/pci/endpoint/functions/pci-epf-ntb.c
> > > @@ -2075,11 +2075,12 @@ static struct config_group *epf_ntb_add_cfs(struct pci_epf *epf,
> > > /**
> > > * epf_ntb_probe() - Probe NTB function driver
> > > * @epf: NTB endpoint function device
> > > + * @id: NTB endpoint function device ID
> > > *
> > > * Probe NTB function driver when endpoint function bus detects a NTB
> > > * endpoint function.
> > > */
> > > -static int epf_ntb_probe(struct pci_epf *epf)
> > > +static int epf_ntb_probe(struct pci_epf *epf, const struct pci_epf_device_id *id)
> > > {
> > > struct epf_ntb *ntb;
> > > struct device *dev;
> > > diff --git a/drivers/pci/endpoint/functions/pci-epf-test.c b/drivers/pci/endpoint/functions/pci-epf-test.c
> > > index 0f9d2ec822ac..d5fcc78a5b73 100644
> > > --- a/drivers/pci/endpoint/functions/pci-epf-test.c
> > > +++ b/drivers/pci/endpoint/functions/pci-epf-test.c
> > > @@ -980,7 +980,7 @@ static const struct pci_epf_device_id pci_epf_test_ids[] = {
> > > {},
> > > };
> > >
> > > -static int pci_epf_test_probe(struct pci_epf *epf)
> > > +static int pci_epf_test_probe(struct pci_epf *epf, const struct pci_epf_device_id *id)
> > > {
> > > struct pci_epf_test *epf_test;
> > > struct device *dev = &epf->dev;
> > > diff --git a/drivers/pci/endpoint/functions/pci-epf-vntb.c b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > > index b7c7a8af99f4..122eb7a12028 100644
> > > --- a/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > > +++ b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > > @@ -1401,7 +1401,7 @@ static struct pci_epf_ops epf_ntb_ops = {
> > > *
> > > * Returns: Zero for success, or an error code in case of failure
> > > */
> > > -static int epf_ntb_probe(struct pci_epf *epf)
> > > +static int epf_ntb_probe(struct pci_epf *epf, const struct pci_epf_device_id *id)
> > > {
> > > struct epf_ntb *ntb;
> > > struct device *dev;
> > > diff --git a/drivers/pci/endpoint/pci-epf-core.c b/drivers/pci/endpoint/pci-epf-core.c
> > > index 2036e38be093..ea6e0aef0bb3 100644
> > > --- a/drivers/pci/endpoint/pci-epf-core.c
> > > +++ b/drivers/pci/endpoint/pci-epf-core.c
> > > @@ -493,16 +493,16 @@ static const struct device_type pci_epf_type = {
> > > .release = pci_epf_dev_release,
> > > };
> > >
> > > -static int
> > > -pci_epf_match_id(const struct pci_epf_device_id *id, const struct pci_epf *epf)
> > > +static const struct pci_epf_device_id
> > > +*pci_epf_match_id(const struct pci_epf_device_id *id, const struct pci_epf *epf)
> > > {
> > > while (id->name[0]) {
> > > if (strcmp(epf->name, id->name) == 0)
> > > - return true;
> > > + return id;
> > > id++;
> > > }
> > >
> > > - return false;
> > > + return NULL;
> > > }
> > >
> > > static int pci_epf_device_match(struct device *dev, struct device_driver *drv)
> > > @@ -510,8 +510,12 @@ static int pci_epf_device_match(struct device *dev, struct device_driver *drv)
> > > struct pci_epf *epf = to_pci_epf(dev);
> > > struct pci_epf_driver *driver = to_pci_epf_driver(drv);
> > >
> > > - if (driver->id_table)
> > > - return pci_epf_match_id(driver->id_table, epf);
> > > + if (driver->id_table) {
> > > + if (pci_epf_match_id(driver->id_table, epf))
> > > + return true;
> > > + else
> > > + return false;
> > > + }
> > >
> > > return !strcmp(epf->name, drv->name);
> > > }
> > > @@ -526,7 +530,7 @@ static int pci_epf_device_probe(struct device *dev)
> > >
> > > epf->driver = driver;
> > >
> > > - return driver->probe(epf);
> > > + return driver->probe(epf, pci_epf_match_id(driver->id_table, epf));
> >
> > I don't think we should do it this way. If we are probing a driver that
> > means that we have got a driver that matches a device id. The device id
> > is a property of the device, there is no reason why we should pass it
> > to the probe function, it has got to be stored somewhere at device
> > creation stage (well, not in the match function - since that's what
> > we changed), probe() should retrieve it from the device structure.
> >
>
> Device id defined by the drivers will only be known during the match() stage as
> that's when the drivers are queried for match of the device. During device
> creation stage, there is no way for the EPF core to fetch the ids.
>
> And, passing id during probe() is not new. For most of the non-platform devices,
> the bus driver will pass the id. The PCI core itself is doing the same for the
> client drivers as well and I'd like to keep it same for EPF also:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/pci.h#n921
Right - I mixed things up (driver->probe() vs bus->probe), apologies,
it makes sense.
Lorenzo
>
> - Mani
>
> > Thanks,
> > Lorenzo
> >
> > > }
> > >
> > > static void pci_epf_device_remove(struct device *dev)
> > > diff --git a/include/linux/pci-epf.h b/include/linux/pci-epf.h
> > > index a215dc8ce693..bc613f0df7e3 100644
> > > --- a/include/linux/pci-epf.h
> > > +++ b/include/linux/pci-epf.h
> > > @@ -89,7 +89,7 @@ struct pci_epc_event_ops {
> > > * @id_table: identifies EPF devices for probing
> > > */
> > > struct pci_epf_driver {
> > > - int (*probe)(struct pci_epf *epf);
> > > + int (*probe)(struct pci_epf *epf, const struct pci_epf_device_id *id);
> > > void (*remove)(struct pci_epf *epf);
> > >
> > > struct device_driver driver;
> > > @@ -131,6 +131,7 @@ struct pci_epf_bar {
> > > * @epc: the EPC device to which this EPF device is bound
> > > * @epf_pf: the physical EPF device to which this virtual EPF device is bound
> > > * @driver: the EPF driver to which this EPF device is bound
> > > + * @id: Pointer to the EPF device ID
> > > * @list: to add pci_epf as a list of PCI endpoint functions to pci_epc
> > > * @lock: mutex to protect pci_epf_ops
> > > * @sec_epc: the secondary EPC device to which this EPF device is bound
> > > @@ -158,6 +159,7 @@ struct pci_epf {
> > > struct pci_epc *epc;
> > > struct pci_epf *epf_pf;
> > > struct pci_epf_driver *driver;
> > > + const struct pci_epf_device_id *id;
> > > struct list_head list;
> > > /* mutex to protect against concurrent access of pci_epf_ops */
> > > struct mutex lock;
> > > --
> > > 2.25.1
> > >
>
> --
> மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-06-05 13:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 11:47 [PATCH v6 0/9] Add support for MHI Endpoint function driver Manivannan Sadhasivam
2023-06-02 11:47 ` [PATCH v6 1/9] PCI: endpoint: Add missing documentation about the MSI/MSI-X range Manivannan Sadhasivam
2023-06-02 11:47 ` [PATCH v6 2/9] PCI: endpoint: Pass EPF device ID to the probe function Manivannan Sadhasivam
2023-06-02 12:13 ` Damien Le Moal
2023-06-05 13:08 ` Lorenzo Pieralisi
2023-06-05 13:55 ` Manivannan Sadhasivam
2023-06-05 9:27 ` Lorenzo Pieralisi
2023-06-05 11:57 ` Manivannan Sadhasivam
2023-06-05 13:06 ` Lorenzo Pieralisi [this message]
2023-06-23 20:14 ` Bjorn Helgaas
2023-06-02 11:47 ` [PATCH v6 3/9] PCI: endpoint: Return error if EPC is started/stopped multiple times Manivannan Sadhasivam
2023-06-02 12:14 ` Damien Le Moal
2023-06-02 11:47 ` [PATCH v6 4/9] PCI: endpoint: Add linkdown notifier support Manivannan Sadhasivam
2023-06-02 11:47 ` [PATCH v6 5/9] PCI: endpoint: Add BME " Manivannan Sadhasivam
2023-06-02 11:47 ` [PATCH v6 6/9] PCI: qcom-ep: Add support for Link down notification Manivannan Sadhasivam
2023-06-02 11:47 ` [PATCH v6 7/9] PCI: qcom-ep: Add support for BME notification Manivannan Sadhasivam
2023-06-02 11:47 ` [PATCH v6 8/9] PCI: endpoint: Add PCI Endpoint function driver for MHI bus Manivannan Sadhasivam
2023-06-07 20:49 ` Bjorn Helgaas
2023-06-07 21:19 ` Bjorn Helgaas
2023-06-08 16:35 ` Manivannan Sadhasivam
2023-06-09 7:53 ` Lorenzo Pieralisi
2023-06-02 11:47 ` [PATCH v6 9/9] MAINTAINERS: Add PCI MHI endpoint function driver under " Manivannan Sadhasivam
2023-06-02 12:15 ` Damien Le Moal
2023-06-05 14:45 ` [PATCH v6 0/9] Add support for MHI Endpoint function driver Lorenzo Pieralisi
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=ZH3d8S1V3u8ppM62@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=bhelgaas@google.com \
--cc=dlemoal@kernel.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.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