From: Mark Brown <broonie@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Alexandre Courbot <gnurou@gmail.com>,
Benoit Parrot <bparrot@ti.com>,
Pantelis Antoniou <panto@antoniou-consulting.com>,
Jiri Prchal <jiri.prchal@aksignal.cz>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [Patch v2 1/2] gpio: add GPIO hogging mechanism
Date: Mon, 12 Jan 2015 12:45:37 +0000 [thread overview]
Message-ID: <20150112124537.GH4160@sirena.org.uk> (raw)
In-Reply-To: <CACRpkdYuRSi8B7jr2F1zYZB4OHvpH9EXOmU0qGa9+O77gcNA7g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
On Mon, Jan 12, 2015 at 10:40:04AM +0100, Linus Walleij wrote:
> On Tue, Dec 2, 2014 at 5:12 PM, Maxime Ripard
> > We do have one board where we have a pin (let's say GPIO14 of the bank
> > A) that enables a regulator that will provide VCC the bank B.
> I think it's a hog in this case though, not a GPIO regulator,
> definately not both. But let's check Mark's opinion on this.
I'm lacking some context here but my first thought is that if VCC might
be supplied by some other thing we need to use a regulator since
otherwise we can't substitute in the other regulator.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-12 12:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 23:54 [Patch v2 0/2] " Benoit Parrot
2014-11-20 23:54 ` [Patch v2 1/2] " Benoit Parrot
2014-11-28 7:30 ` Alexandre Courbot
2014-12-01 16:36 ` Maxime Ripard
2014-12-02 0:27 ` Benoit Parrot
2014-12-02 14:13 ` Alexandre Courbot
2014-12-02 14:29 ` Linus Walleij
2014-12-02 16:12 ` Maxime Ripard
2014-12-04 14:15 ` Alexandre Courbot
2014-12-04 14:27 ` Pantelis Antoniou
2014-12-04 14:41 ` Alexandre Courbot
2014-12-04 14:47 ` Pantelis Antoniou
2014-12-04 14:58 ` Alexandre Courbot
2014-12-04 15:02 ` Pantelis Antoniou
2014-12-04 15:10 ` Alexandre Courbot
2014-12-04 15:22 ` Pantelis Antoniou
2014-12-06 12:04 ` Alexandre Courbot
2014-12-04 14:27 ` Maxime Ripard
2014-12-04 14:49 ` Alexandre Courbot
2014-12-05 10:24 ` Maxime Ripard
2014-12-06 12:08 ` Alexandre Courbot
2014-12-08 19:18 ` Maxime Ripard
2014-12-04 14:52 ` Maxime Ripard
2014-12-04 15:00 ` Alexandre Courbot
2015-01-12 9:40 ` Linus Walleij
2015-01-12 12:45 ` Mark Brown [this message]
2014-12-02 0:22 ` Benoit Parrot
2014-12-02 14:10 ` Alexandre Courbot
2014-12-02 14:28 ` Linus Walleij
2014-12-02 14:25 ` Linus Walleij
2014-11-20 23:54 ` [Patch v2 2/2] gpio: Document " Benoit Parrot
2014-11-28 7:31 ` Alexandre Courbot
2014-12-01 22:57 ` Benoit Parrot
2014-12-02 14:04 ` Alexandre Courbot
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=20150112124537.GH4160@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jiri.prchal@aksignal.cz \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=panto@antoniou-consulting.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
all inboxes | Powered by JetHome®