linux-kernel - Re: [v2 2/4] platform: (TS-5500) add GPIO support

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:	Tue, 30 Aug 2011 10:49:55 -0400
From:	Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	Jerome Oufella <jerome.oufella@...oirfairelinux.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [v2 2/4] platform: (TS-5500) add GPIO support

On Tue, 30 Aug 2011 12:00:20 +0100,
Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:

> On Mon, Aug 29, 2011 at 10:36:32PM -0700, H. Peter Anvin wrote:
> > On 08/29/2011 03:11 PM, Mark Brown wrote:
> 
> > > New GPIO drivers should really go under drivers/gpiolib and be
> > > called gpio-foo.c.
> 
> > Should they?  It seems a lot more reasonable to have them collected
> > by platform than by type of device (GPIO), *unless* they are shared.

Grouping every driver for this platform was one of the main comments of
my first RFC set of patches. And indeed, the GPIO driver is really
specific to this platform, so it won't be shared.

	Vivien.
> 
> There was some discussion of this, mostly for ARM, the general
> conclusion being that sharing the code improves visibility of things
> for the subsystem maintainer, ensures that the code gets reviewed (and
> updated if things change) by subsystem experts and makes it more
> likely that where there are things that can be shared someone will
> notice.
--
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/