linux-kernel - Re: [PATCH 2/6] regulator: of: Add enable GPIO configuration function

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:	Wed, 22 Jun 2016 11:35:32 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Alexandre Courbot <acourbot@...dia.com>
Cc:	Liam Girdwood <lgirdwood@...il.com>,
	Rob Herring <robh+dt@...nel.org>,
	Mark Rutland <mark.rutland@....com>,
	linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
	gnurou@...il.com
Subject: Re: [PATCH 2/6] regulator: of: Add enable GPIO configuration function

On Wed, Jun 22, 2016 at 05:25:54PM +0900, Alexandre Courbot wrote:
> Several regulator drivers are using an enable GPIO with similar DT
> properties, yet each driver is parsing these properties its own way. Add
> the of_get_regulator_gpio_config() function which is able to parse all
> known properties and update the regulator_config accordingly.

Why is this a function and not something data driven in the core?

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