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  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, 25 Jun 2013 10:12:01 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Chao Xie <xiechao.mail@...il.com>
Cc:	Chao Xie <chao.xie@...vell.com>, lgirdwood@...il.com,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	yizhang@...vell.com
Subject: Re: [PATCH V2] regulator: 88pm800: add regulator driver for 88pm800

On Tue, Jun 25, 2013 at 10:13:38AM +0800, Chao Xie wrote:
> On Mon, Jun 24, 2013 at 6:14 PM, Mark Brown <broonie@...nel.org> wrote:

> > If you really need to have platform data for all the regulators then
> > just embed the array inside the platform data so there's no possibility
> > of any confusion.

> Some regulators will not be exported to kernel depending on boards which are
> for special usage. So i do not use a array inside the platform data.

Remember that the regulator API won't do anything except read from a
regulator unless it's got constraints saying it's OK to do so.  Are you
saying that even reading the hardware state is a problem?

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists