[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM6PR11MB2841976B8E89C980CCC29AD2DD0B0@DM6PR11MB2841.namprd11.prod.outlook.com>
Date: Thu, 8 Oct 2020 22:04:12 +0000
From: "Ertman, David M" <david.m.ertman@...el.com>
To: Leon Romanovsky <leon@...nel.org>
CC: "alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"tiwai@...e.de" <tiwai@...e.de>,
"broonie@...nel.org" <broonie@...nel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"jgg@...dia.com" <jgg@...dia.com>,
"dledford@...hat.com" <dledford@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"ranjani.sridharan@...ux.intel.com"
<ranjani.sridharan@...ux.intel.com>,
"pierre-louis.bossart@...ux.intel.com"
<pierre-louis.bossart@...ux.intel.com>,
"fred.oh@...ux.intel.com" <fred.oh@...ux.intel.com>,
"parav@...lanox.com" <parav@...lanox.com>,
"Saleem, Shiraz" <shiraz.saleem@...el.com>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"Patil, Kiran" <kiran.patil@...el.com>
Subject: RE: [PATCH v2 1/6] Add ancillary bus support
> -----Original Message-----
> From: Leon Romanovsky <leon@...nel.org>
> Sent: Tuesday, October 6, 2020 10:23 AM
> To: Ertman, David M <david.m.ertman@...el.com>
> Cc: alsa-devel@...a-project.org; tiwai@...e.de; broonie@...nel.org; linux-
> rdma@...r.kernel.org; jgg@...dia.com; dledford@...hat.com;
> netdev@...r.kernel.org; davem@...emloft.net; kuba@...nel.org;
> gregkh@...uxfoundation.org; ranjani.sridharan@...ux.intel.com; pierre-
> louis.bossart@...ux.intel.com; fred.oh@...ux.intel.com;
> parav@...lanox.com; Saleem, Shiraz <shiraz.saleem@...el.com>; Williams,
> Dan J <dan.j.williams@...el.com>; Patil, Kiran <kiran.patil@...el.com>
> Subject: Re: [PATCH v2 1/6] Add ancillary bus support
>
> On Mon, Oct 05, 2020 at 11:24:41AM -0700, Dave Ertman wrote:
> > Add support for the Ancillary Bus, ancillary_device and ancillary_driver.
> > It enables drivers to create an ancillary_device and bind an
> > ancillary_driver to it.
> >
> > The bus supports probe/remove shutdown and suspend/resume callbacks.
> > Each ancillary_device has a unique string based id; driver binds to
> > an ancillary_device based on this id through the bus.
> >
> > Co-developed-by: Kiran Patil <kiran.patil@...el.com>
> > Signed-off-by: Kiran Patil <kiran.patil@...el.com>
> > Co-developed-by: Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>
> > Signed-off-by: Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>
> > Co-developed-by: Fred Oh <fred.oh@...ux.intel.com>
> > Signed-off-by: Fred Oh <fred.oh@...ux.intel.com>
> > Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
> > Reviewed-by: Shiraz Saleem <shiraz.saleem@...el.com>
> > Reviewed-by: Parav Pandit <parav@...lanox.com>
> > Reviewed-by: Dan Williams <dan.j.williams@...el.com>
> > Signed-off-by: Dave Ertman <david.m.ertman@...el.com>
> > ---
>
> <...>
>
> > +/**
> > + * __ancillary_driver_register - register a driver for ancillary bus devices
> > + * @ancildrv: ancillary_driver structure
> > + * @owner: owning module/driver
> > + */
> > +int __ancillary_driver_register(struct ancillary_driver *ancildrv, struct
> module *owner)
> > +{
> > + if (WARN_ON(!ancildrv->probe) || WARN_ON(!ancildrv->remove)
> ||
> > + WARN_ON(!ancildrv->shutdown) || WARN_ON(!ancildrv-
> >id_table))
> > + return -EINVAL;
>
> In our driver ->shutdown is empty, it will be best if ancillary bus will
> do "if (->remove) ..->remove()" pattern.
>
Yes, looking it over, only the probe needs to mandatory. I will change the others to the
conditional model, and adjust the WARN_ONs.
> > +
> > + ancildrv->driver.owner = owner;
> > + ancildrv->driver.bus = &ancillary_bus_type;
> > + ancildrv->driver.probe = ancillary_probe_driver;
> > + ancildrv->driver.remove = ancillary_remove_driver;
> > + ancildrv->driver.shutdown = ancillary_shutdown_driver;
> > +
>
> I think that this part is wrong, probe/remove/shutdown functions should
> come from ancillary_bus_type.
>From checking other usage cases, this is the model that is used for probe, remove,
and shutdown in drivers. Here is the example from Greybus.
int greybus_register_driver(struct greybus_driver *driver, struct module *owner,
const char *mod_name)
{
int retval;
if (greybus_disabled())
return -ENODEV;
driver->driver.bus = &greybus_bus_type;
driver->driver.name = driver->name;
driver->driver.probe = greybus_probe;
driver->driver.remove = greybus_remove;
driver->driver.owner = owner;
driver->driver.mod_name = mod_name;
> You are overwriting private device_driver
> callbacks that makes impossible to make container_of of ancillary_driver
> to chain operations.
>
I am sorry, you lost me here. you cannot perform container_of on the callbacks
because they are pointers, but if you are referring to going from device_driver
to the auxiliary_driver, that is what happens in auxiliary_probe_driver in the
very beginning.
static int auxiliary_probe_driver(struct device *dev)
145 {
146 struct auxiliary_driver *auxdrv = to_auxiliary_drv(dev->driver);
147 struct auxiliary_device *auxdev = to_auxiliary_dev(dev);
Did I miss your meaning?
-DaveE
> > + return driver_register(&ancildrv->driver);
> > +}
> > +EXPORT_SYMBOL_GPL(__ancillary_driver_register);
>
> Thanks
Powered by blists - more mailing lists