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:58:28 +0100
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Thomas Renninger" <trenn@...e.de>
Cc:	"Pavel Machek" <pavel@...e.cz>,
	"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 Mon, Oct 27, 2008 at 13:45, Thomas Renninger <trenn@...e.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
--
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/