From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Chen <peter.chen@nxp.com>
Cc: Bastien Nocera <hadess@hadess.net>,
Alan Stern <stern@rowland.harvard.edu>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 1/2] USB: Fix device driver race
Date: Thu, 23 Jul 2020 12:49:32 +0200 [thread overview]
Message-ID: <20200723104932.GA1949100@kroah.com> (raw)
In-Reply-To: <AM7PR04MB71570D838FDDB467A302423E8B760@AM7PR04MB7157.eurprd04.prod.outlook.com>
On Thu, Jul 23, 2020 at 10:35:30AM +0000, Peter Chen wrote:
>
> > > > > > After that, nothing will trigger a reprobe when the modprobe()'d
> > > > > > device driver has finished initialising, as the device has the
> > > > > > "generic"
> > > > > > driver attached to it.
> > > > > >
> > > > > > Trigger a reprobe ourselves when new specialised drivers get
> > > > > > registered.
> > > > > >
> > > > > > Signed-off-by: Bastien Nocera <hadess@hadess.net>
> > > > > > ---
> > > > > > drivers/usb/core/driver.c | 31 +++++++++++++++++++++++++++++--
> > > > > > 1 file changed, 29 insertions(+), 2 deletions(-)
> > > > > >
> > > > > > diff --git a/drivers/usb/core/driver.c
> > > > > > b/drivers/usb/core/driver.c index f81606c6a35b..a6187dd2186c
> > > > > > 100644
> > > > > > --- a/drivers/usb/core/driver.c
> > > > > > +++ b/drivers/usb/core/driver.c
> > > > > > @@ -905,6 +905,30 @@ static int usb_uevent(struct device *dev,
> > > > > > struct kobj_uevent_env *env)
> > > > > > return 0;
> > > > > > }
> > > > > >
> > > > > > +static int __usb_bus_reprobe_drivers(struct device *dev, void
> > > > > > *data)
> > > > > > +{
> > > > > > + struct usb_device_driver *udriver =
> > > > > > to_usb_device_driver(dev-
> > > > > > > driver);
> > > > > > + struct usb_device *udev = to_usb_device(dev);
> > > > > > +
> > > > > > + if (udriver == &usb_generic_driver &&
> > > > > > + !udev->use_generic_driver)
> > > > > > + return device_reprobe(dev);
> > > > > > +
> > > > > > + return 0;
> > > > > > +}
> > > > > > +
> > > > > > +static int __usb_device_driver_added(struct device_driver
> > > > > > *drv,
> > > > > > void *data)
> > > > > > +{
> > > > > > + struct usb_device_driver *udrv =
> > > > > > to_usb_device_driver(drv);
> > > > > > +
> > > > > > + if (udrv->match) {
> > > > > > + bus_for_each_dev(&usb_bus_type, NULL, udrv,
> > > > > > + __usb_bus_reprobe_drivers);
> > > > >
> > > > > What does udrv get used for here?
> > > > >
> > > > > > + }
> > > > > > +
> > > > > > + return 0;
> > > > > > +}
> > > > > > +
> > > > > > /**
> > > > > > * usb_register_device_driver - register a USB device (not
> > > > > > interface) driver
> > > > > > * @new_udriver: USB operations for the device driver @@
> > > > > > -934,13 +958,16 @@ int usb_register_device_driver(struct
> > > > > > usb_device_driver *new_udriver,
> > > > > >
> > > > > > retval = driver_register(&new_udriver->drvwrap.driver);
> > > > > >
> > > > > > - if (!retval)
> > > > > > + if (!retval) {
> > > > > > + bus_for_each_drv(&usb_bus_type, NULL, NULL,
> > > > > > + __usb_device_driver_added);
> > > > >
> > > > > This looks funny. You're calling both bus_for_each_drv() and
> > > > > bus_for_each_dev(). Can't you skip this iterator and just call
> > > > > bus_for_each_dev() directly?
> > > >
> > > > You're right, looks like this could be simplified somewhat. I'm
> > > > building and testing a smaller patch.
> > > >
> > >
> > > What do you mean "reprobe" for your device? Do you mean the
> > > mfi_fc_probe is not called? If it is, Would you please check why
> > > usb_device_match at drivers/usb/core/driver.c does not return true for
> > > your device?
> >
> > mfi_fc_probe() isn't called because the device already has the generic driver
> > attached by the time the apple-mfi-fastcharge driver is loaded.
>
> Would you please explain more, why only this driver has this issue? Seem you
> create a struct usb_device_driver, but not struct usb_driver, few drivers do like
> that. You may see drivers/usb/misc/ehset.c and drivers/usb/misc/appledisplay.c
> as an example.
This is a different "type" of driver.
next prev parent reply other threads:[~2020-07-23 10:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 9:46 [PATCH 1/2] USB: Fix device driver race Bastien Nocera
2020-07-22 9:46 ` [PATCH 2/2] USB: Fix source path in header Bastien Nocera
2020-07-22 9:51 ` Greg Kroah-Hartman
2020-07-22 9:58 ` Bastien Nocera
2020-07-22 10:35 ` Greg Kroah-Hartman
2020-07-22 10:56 ` Bastien Nocera
2020-07-22 11:12 ` [PATCH 1/2] USB: Fix device driver race Greg Kroah-Hartman
2020-07-22 11:18 ` Bastien Nocera
2020-07-22 15:26 ` Alan Stern
2020-07-22 15:53 ` Bastien Nocera
2020-07-23 2:19 ` Peter Chen
2020-07-23 9:02 ` Bastien Nocera
2020-07-23 10:35 ` Peter Chen
2020-07-23 10:49 ` Greg Kroah-Hartman [this message]
2020-07-23 10:57 ` Bastien Nocera
2020-07-23 12:12 ` Peter Chen
2020-07-23 12:14 ` Bastien Nocera
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=20200723104932.GA1949100@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.com \
--cc=stern@rowland.harvard.edu \
/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