linux-kernel - Re: Fundamental Design Flaw of the Device Driver Model?

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:	Fri, 22 Aug 2008 20:56:16 -0400
From:	"Eric Miao" <eric.y.miao@...il.com>
To:	"pHilipp Zabel" <philipp.zabel@...il.com>
Cc:	"Pavel Machek" <pavel@...e.cz>,
	LKML <linux-kernel@...r.kernel.org>,
	"Samuel Ortiz" <sameo@...nedhand.com>
Subject: Re: Fundamental Design Flaw of the Device Driver Model?

> Instead of allocating/adding the platform subdevices manually in
> da903x_add_subdevs, couldn't you use the MFD (multi function device)
> infrastructure that seems to be intended for this case? Also, I think
> that the da9030 base driver would then better fit in drivers/mfd, not
> drivers/i2c/chips (didn't Jean Delvare himself state that ideally
> drivers/i2c/chips should be empty?).

Actually, I don't mind keep it anywhere. The intermediate
platform_device is what I'd like to avoid mostly. Using my
own simple logic allows me to do that later.
--
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/