From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Fwd: Question about USB hotplug
Date: Sat, 14 Jun 2014 07:36:22 -0700 [thread overview]
Message-ID: <20140614143622.GB20718@kroah.com> (raw)
In-Reply-To: <539BBA6D.7030206@gmail.com>
On Sat, Jun 14, 2014 at 10:58:53AM +0800, Simon Guo wrote:
> Forward to USB mail alias for the USB question.
>
> -------- Original post --------
> Subject: Question about USB hotplug
> Date: Sat, 14 Jun 2014 09:59:45 +0800
> Sender: Simon Guo <wei.guo.simon@gmail.com>
> Receiver: kernelnewbies at kernelnewbies.org, wei.guo.simon at gmail.com
>
> Hi, dear list,
>
> I want to be clear about the USB hotplug procedure.
>
> I read "Linux Device Driver" and "Documentation/usb/hotplug.txt", and
> google much. Per my understanding, the USB hotplug works as following:
> 1) Insertion of physical U-disk will trigger a hardware interrupt. And
> interrupt handler (installed by USB bus driver?) will create kobj at /sys.
> 2) According to Linux device model, the creation of kobj will raise
> hotplug event (implemented in USB bus driver).
> 3) user space hotplug helper is invoked to handle hotplug event. Hotplug
> helper will read "modules.usbmaps" and decide to load which USB driver.
> If there are many drivers matching the device, they will all be loaded?
> 4) udev will create approparite dev under /dev according to rules defined.
> Please correct me if I am wrong in the above.
>
> I am using Ubuntu 11, and with my own build kernel version 3.15.0.
Please ask on a Ubuntu mailing list, they are the only distro that
people have problems with this, so they must be doing something "odd"
compared to everyone else.
sorry,
greg k-h
next prev parent reply other threads:[~2014-06-14 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 1:59 Question about USB hotplug Simon Guo
2014-06-14 2:58 ` Fwd: " Simon Guo
2014-06-14 14:36 ` Greg KH [this message]
2014-06-16 12:53 ` Simon Guo
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=20140614143622.GB20718@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).