From: Eric Piel <eric.piel@tremplin-utc.net>
To: Pavel Machek <pavel@suse.cz>
Cc: Thomas Renninger <trenn@suse.de>,
akpm@linux-foundation.org, burman.yan@gmail.com,
rpurdie@rpsys.net, LKML <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>
Subject: leds-hp-disk vs lis3lv02d
Date: Sat, 25 Oct 2008 12:42:31 +0200 [thread overview]
Message-ID: <4902F817.4050108@tremplin-utc.net> (raw)
In-Reply-To: <20081019204819.GC1465@ucw.cz>
Pavel Machek schreef:
> Hi!
>
>> shouldn't this one be integrated into Eric's/Yan's driver?
>
> It is separate piece of hardware, completely unrelated to lids3v
> chip. No, it should not be integrated, but I'll makesure they work
> toggether well.
Hello,
I think I talked too fast: it seems impossible to have both drivers
(leds-hp-disk and lis3lv02d) working at the same time. Only the first
driver loaded is used.
After a little look at it, I think it comes from the fact that both
drivers are assigned to the same MODALIAS (HPQ0004). The ACPI PNP
(through the generic bus infrastructure) only declare the device to one
of the drivers supporting it, not all of them.
How can I tell to ACPI that it should load both drivers for the same PNP
ID match?
Eric
next parent reply other threads:[~2008-10-25 10:42 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 [this message]
2008-10-26 17:40 ` leds-hp-disk vs lis3lv02d Pavel Machek
2008-10-27 12:45 ` Thomas Renninger
2008-10-27 12:58 ` Kay Sievers
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=4902F817.4050108@tremplin-utc.net \
--to=eric.piel@tremplin-utc.net \
--cc=akpm@linux-foundation.org \
--cc=burman.yan@gmail.com \
--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