linux-kernel - Re: [PATCH 2/2] regulator: core: Allow enable GPIO to be specified using GPIOD

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: <20161129115306.GI1867@localhost.localdomain>
Date:   Tue, 29 Nov 2016 11:53:06 +0000
From:   Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To:     Mark Brown <broonie@...nel.org>
CC:     <lgirdwood@...il.com>, <linux-kernel@...r.kernel.org>,
        <patches@...nsource.wolfsonmicro.com>
Subject: Re: [PATCH 2/2] regulator: core: Allow enable GPIO to be specified
 using GPIOD

On Tue, Nov 29, 2016 at 11:45:47AM +0000, Mark Brown wrote:
> On Tue, Nov 29, 2016 at 11:30:45AM +0000, Charles Keepax wrote:
> > The regulator subsystem has used GPIOs internally for a while, however,
> > end drivers must still specify their enable GPIO using a GPIO number. This
> > patch allows the end drivers to specify the enable GPIO using GPIOD
> > directly.
> 
> The reason we don't support descriptors is that the GPIO API currently
> doesn't support having more than one user of a descriptor but GPIO
> enables for regulators get shared often enough to be interesting.  If
> drivers start using this then that'd mean that the shared enable support
> would become erratic depending on which driver was in use.

Ah ok thanks, guess we can drop this one then. The first patch in
the chain is hopefully still good though.

Thanks,
Charles