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] [day] [month] [year] [list]
Message-ID: <20090731135036.GA626@rakim.wolfsonmicro.main>
Date:	Fri, 31 Jul 2009 14:50:36 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Roger Quadros <quadros.roger@...il.com>
Cc:	pHilipp Zabel <philipp.zabel@...il.com>, lrg@...mlogic.co.uk,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: Add GPIO enable control to fixed voltage
 regulator driver

On Fri, Jul 31, 2009 at 04:43:40PM +0300, Roger Quadros wrote:
> On Fri, Jul 31, 2009 at 4:34 PM, Mark
> Brown<broonie@...nsource.wolfsonmicro.com> wrote:

> > Feh, better print a warning for GPIO 0 for at least a kernel release.
> > Fortunately we've got no mainline users of fixed voltage regulators.

> I think most architectures start their GPIO numbering from 0.
> By 'a release', do you mean next Kernel release will be indexing GPIOs from 1?

No; I mean the driver should print a warning when using GPIO 0 as a way
of managing the transition.  Otherwise any existing users will find the
driver suddenly starts using a GPIO.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ