From: Mark Brown <broonie@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH] gpio/regulator: Allow nonexclusive GPIO access
Date: Fri, 12 Oct 2018 18:10:15 +0200 [thread overview]
Message-ID: <20181012161015.GB2340@sirena.org.uk> (raw)
In-Reply-To: <CACRpkdY=ya9CJz0HbsdgzR+05SdoHQ+V17fY8sBtNtF482eXew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
On Thu, Oct 11, 2018 at 08:41:16PM +0200, Linus Walleij wrote:
> On Thu, Oct 11, 2018 at 7:54 PM Mark Brown <broonie@kernel.org> wrote:
> > Other regulators that have GPIO control for their enables do their own
> > requests (as does the core) so don't they all need to set the flag
> > GPIOD_FLAGS_BIT_NONEXCLUSIVE when they request otherwise it'll only work
> > in systems where the regulators after the first that request the GPIO
> > are fixed regulators?
> Yeah ... I guess I assumed that the same enable line is not used
> for a fixed regulator and then some other regulator (which is not
> fixed).
> If this is common practice we need to account for it. Obviously
> I have no idea what is common practice :/
> Do we know some way to identify the affected systems or
> should we just tag on GPIOD_FLAGS_BIT_NONEXCLUSIVE
> on all the stuff we converted to descs to play it safe?
> (I can cook a patch.)
I think we need to set the flag everywhere, previously we'd essentially
been doing it by asking the GPIO framework if we resolved the same
regulator as one we already had.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-12 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181011143542epcas1p24f7b9193acf33746a2fc166bf63a8f77@epcas1p2.samsung.com>
2018-10-11 14:35 ` Linus Walleij
2018-10-11 14:43 ` Mark Brown
2018-10-11 17:01 ` Linus Walleij
2018-10-11 17:54 ` Mark Brown
2018-10-11 18:41 ` Linus Walleij
2018-10-12 16:10 ` Mark Brown [this message]
2018-10-11 15:15 ` Marek Szyprowski
2018-10-12 10:30 ` Jon Hunter
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=20181012161015.GB2340@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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®