From: Hritik Vijay <hritikxx8@gmail.com>
To: linux-usb@vger.kernel.org
Subject: Order in which kernel decides binding device driver
Date: Sun, 16 May 2021 02:22:22 +0530 [thread overview]
Message-ID: <YKA0hphGFeqM+BZG@Journey.localdomain> (raw)
Hello
I've experimented with two device drivers targeting a single device,
both hot-pluggable. When the device plugs in, both the modules are loaded.
This is expected behavior of udev. After being loaded, only one of the
drivers offered by them is chosen to be bound to the device
i.e. only one module gets to execute their `probe` function.
I tried looking through the source to find out which module would get
the preference but I would really like some clarification on the
topic.
In what order will the kernel decide to give opportunities to device
drivers to bind to a device ?
Hrtk
next reply other threads:[~2021-05-15 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 20:52 Hritik Vijay [this message]
2021-05-16 1:01 ` Order in which kernel decides binding device driver Alan Stern
[not found] ` <YKCovrGBB4QQAl52@Journey.localdomain>
2021-05-16 14:41 ` Alan Stern
2021-05-17 8:07 ` Hritik Vijay
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=YKA0hphGFeqM+BZG@Journey.localdomain \
--to=hritikxx8@gmail.com \
--cc=linux-usb@vger.kernel.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