linux-kernel - Re: [PATCH] twl-regulator: Allow CONFIG_TWL4030_ALLOW

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]

Message-ID: <20120425101258.GI3195@opensource.wolfsonmicro.com>
Date:	Wed, 25 Apr 2012 11:12:59 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	NeilBrown <neilb@...e.de>
Cc:	Liam Girdwood <lrg@...com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] twl-regulator: Allow CONFIG_TWL4030_ALLOW_UNSUPPORTED to
 be requested.

On Wed, Apr 25, 2012 at 07:59:56PM +1000, NeilBrown wrote:

> That make sense - but I cannot find a good place to put the flag.
> TWL doesn't have any twl-specific platform data, it just uses
> struct regulator_init_data.  I don't suppose it would be acceptable
> to tuck an 'allow_unsupported' flag inside 'struct regulation_constraints'?

> I'm not sure how else to do it without fairly major surgery.

This is what the driver_data in regulator_init_data is there for - to
allow device specific extensions to be added if needed.  I guess it
should be possible to use that?

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