linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <linux-kernel@vger.kernel.org>,
	<patches@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 2/2] regulator: core: Allow enable GPIO to be specified using GPIOD
Date: Tue, 29 Nov 2016 11:53:06 +0000	[thread overview]
Message-ID: <20161129115306.GI1867@localhost.localdomain> (raw)
In-Reply-To: <20161129114547.erdaezyfvzzdtjuk@sirena.org.uk>

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

  reply	other threads:[~2016-11-29 11:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 11:30 [PATCH 1/2] regulator: core: Correct type of mode in regulator_mode_constrain Charles Keepax
2016-11-29 11:30 ` [PATCH 2/2] regulator: core: Allow enable GPIO to be specified using GPIOD Charles Keepax
2016-11-29 11:38   ` Charles Keepax
2016-11-29 11:45   ` Mark Brown
2016-11-29 11:53     ` Charles Keepax [this message]
2016-11-30 18:07 ` Applied "regulator: core: Correct type of mode in regulator_mode_constrain" to the regulator tree Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161129115306.GI1867@localhost.localdomain \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).