linux-kernel - Re: leds-hp-disk vs lis3lv02d

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 27 Oct 2008 13:45:03 +0100
From:	Thomas Renninger <trenn@...e.de>
To:	Pavel Machek <pavel@...e.cz>
Cc:	Eric Piel <eric.piel@...mplin-utc.net>, akpm@...ux-foundation.org,
	burman.yan@...il.com, rpurdie@...ys.net,
	LKML <linux-kernel@...r.kernel.org>,
	Len Brown <len.brown@...el.com>,
	Kay Sievers <kasievers@...e.de>, hmh@....eng.br
Subject: Re: leds-hp-disk vs lis3lv02d

On Sunday 26 October 2008 18:40:25 Pavel Machek wrote:
> 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.
>
> I can reproduce it here and it obviously needs fixing.
These are the first ACPI drivers who register for the same ACPI Hardware ID.

> OTOH  it should 
> not block merge; both drivers still work and are useful.
But for long-term the HPQ0004 specific things in the lids3v driver should get 
merged with your HP leds driver also registering for HPQ0004 and the lids3v 
specific things should get a separate driver which HPQ0004 driver makes use 
of?
So in the end also for the HPQ0004 device only one driver should register for?
>
> > 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.

     Thomas

Pavel: I am also not sure whether it's a good idea to mis-use the HP's LED for 
mail notification or similar or to expose this one as a general LED. This LED 
is intended to be used with the disk parking feature by the vendor?
I don't know the LED interface well, but if it's now possible that every mail 
or other app can reprogram the disk parking LED for it's own purposes, this 
sounds wrong. The LED can still be accessed and activated, e.g. when disk 
gets parked behind the OS'es back. If this is a nice hack to e.g. use LED for 
suspend debugging or similar, then it should be well hidden to the outside 
world.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/