From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Thomas Renninger" <trenn@suse.de>
Cc: "Pavel Machek" <pavel@suse.cz>,
"Eric Piel" <eric.piel@tremplin-utc.net>,
akpm@linux-foundation.org, burman.yan@gmail.com,
rpurdie@rpsys.net, LKML <linux-kernel@vger.kernel.org>,
"Len Brown" <len.brown@intel.com>,
"Kay Sievers" <kasievers@suse.de>,
hmh@hmh.eng.br
Subject: Re: leds-hp-disk vs lis3lv02d
Date: Mon, 27 Oct 2008 13:58:28 +0100 [thread overview]
Message-ID: <ac3eb2510810270558u52a66aefqe8774c09ffb19296@mail.gmail.com> (raw)
In-Reply-To: <200810271345.04961.trenn@suse.de>
On Mon, Oct 27, 2008 at 13:45, Thomas Renninger <trenn@suse.de> wrote:
> On Sunday 26 October 2008 18:40:25 Pavel Machek wrote:
>> > How can I tell to ACPI that it should load both drivers for the same PNP
>> > ID match?
>>
>> I'll take a look if I can figure something out...
> Kay may know whether this should work and how.
> IMO having several drivers registering for the same HID should get avoided if
> possible, it's confusing.
There is currently no driver core support to bind two "struct device"
to one parent "struct device" from different drivers.
You can work around that by creating a custom "struct bus_type",
create the several function devices there, and let them bind different
drivers. This is what matches a lot of hardware like custom devices
all hiding behind a single PCI device.
Or the code for the two functions must live in the same driver, and
create class devices, so it looks to the core like a single binding.
There is ongoing work in the driver core to allow
multi-driver-binding, but it's not ready to use today.
Kay
next prev parent reply other threads:[~2008-10-27 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200810162255.m9GMtKj4001733@imap1.linux-foundation.org>
[not found] ` <200810192106.15905.trenn@suse.de>
[not found] ` <20081019204819.GC1465@ucw.cz>
2008-10-25 10:42 ` Eric Piel
2008-10-26 17:40 ` Pavel Machek
2008-10-27 12:45 ` Thomas Renninger
2008-10-27 12:58 ` Kay Sievers [this message]
2008-10-27 13:03 ` Pavel Machek
2008-11-06 12:14 ` Pavel Machek
2008-11-06 21:45 ` Éric Piel
2008-11-06 22:22 ` Andrew Morton
2008-11-05 23:00 ` Pavel Machek
2008-11-10 11:59 ` Pavel Machek
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=ac3eb2510810270558u52a66aefqe8774c09ffb19296@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=akpm@linux-foundation.org \
--cc=burman.yan@gmail.com \
--cc=eric.piel@tremplin-utc.net \
--cc=hmh@hmh.eng.br \
--cc=kasievers@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rpurdie@rpsys.net \
--cc=trenn@suse.de \
/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
all inboxes | Powered by JetHome®