From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Julius Werner <jwerner@chromium.org>,
Dan Williams <dcbw@redhat.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
USB Storage list <usb-storage@lists.one-eyed-alien.net>
Subject: Re: [PATCH] usb: storage: Add ums-cros-aoa driver
Date: Mon, 2 Sep 2019 18:47:24 +0200 [thread overview]
Message-ID: <20190902164724.GA22619@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1908301337150.1459-100000@iolanthe.rowland.org>
On Fri, Aug 30, 2019 at 01:43:36PM -0400, Alan Stern wrote:
> > I could instead add a new sysfs node 'force_bind' to the driver core,
> > that would work like 'bind' except for skipping the
> > driver_match_device() call entirely and forcing a probe(). Do you
> > think that would be acceptable? Or is that too big of a hammer to make
> > available for all drivers in Linux? Maybe if I do the same thing but
> > only for usb drivers, or even only for the usb-storage driver
> > specifically, would that be acceptable?
>
> This is a question for Greg. The problem is that there may be drivers
> which can't handle being probed for devices they don't match.
>
> Still, we ought to have a mechanism for doing manual but not automatic
> matches.
>
> Greg, any thoughts?
This should work just fine today. Add a new device id to the "new_id"
file and then tell the driver to bind. That's pretty much the same as a
"force_bind", right?
thanks,
greg k-h
next prev parent reply other threads:[~2019-09-02 16:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 23:14 [PATCH] usb: storage: Add ums-cros-aoa driver Julius Werner
2019-08-27 23:29 ` Matthew Dharm
[not found] ` <CAA6KcBAykS+VkhkcF42PhGyNu8KAEoaYPgA9-ru_HCxKrAEZzg@mail.gmail.com>
2019-08-27 23:59 ` Julius Werner
2019-08-28 8:32 ` Greg Kroah-Hartman
2019-08-28 16:17 ` Alan Stern
2019-08-28 16:41 ` Dan Williams
2019-08-29 3:26 ` Julius Werner
2019-08-29 7:25 ` Greg Kroah-Hartman
2019-08-29 15:41 ` Alan Stern
2019-08-30 0:31 ` Julius Werner
2019-08-30 17:43 ` Alan Stern
2019-09-02 16:47 ` Greg KH [this message]
2019-09-03 8:46 ` Oliver Neukum
2019-09-03 9:19 ` Greg KH
2019-09-03 10:04 ` Oliver Neukum
2019-09-03 12:45 ` Greg KH
2019-09-03 14:14 ` Alan Stern
2019-09-06 21:02 ` Julius Werner
2019-09-07 19:10 ` Alan Stern
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=20190902164724.GA22619@kroah.com \
--to=greg@kroah.com \
--cc=dcbw@redhat.com \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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).