From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Warren <swarren@nvidia.com>,
Grant Likely <grant.likely@secretlab.ca>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
Randy Dunlap <rdunlap@xenotime.net>,
Olof Johansson <olof@lixom.net>, Colin Cross <ccross@android.com>,
Chris Ball <cjb@laptop.org>,
linux-doc@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Documentation/gpio.txt: Explain expected pinctrl interaction
Date: Tue, 21 Feb 2012 11:46:03 +0100 [thread overview]
Message-ID: <CACRpkdbPeVBv5VWefDvib5HmGF0K2gT79Mx7g-yviyQj33+Z-w@mail.gmail.com> (raw)
In-Reply-To: <1329719263-18971-1-git-send-email-swarren@nvidia.com>
On Mon, Feb 20, 2012 at 7:27 AM, Stephen Warren <swarren@nvidia.com> wrote:
> Update gpio.txt based on recent discussions regarding interaction with the
> pinctrl subsystem.
>
> Previously, gpio_request() was described as explicitly not performing any
> required mux setup operations etc.
>
> Now, gpio_request() is explicitly as explicitly performing any required mux
> setup operations where possible. In the case it isn't, platform code is
> required to have set up any required muxing or other configuration prior to
> gpio_request() being called, in order to maintain the same semantics.
>
> This is achieved by gpiolib drivers calling e.g. pinctrl_request_gpio() in
> their .request() operation.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Grant can you take this one? I'd prefer for you to have a look at
it as well.
Yours,
Linus Walleij
next prev parent reply other threads:[~2012-02-21 10:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 6:27 [PATCH 1/2] Documentation/gpio.txt: Explain expected pinctrl interaction Stephen Warren
2012-02-20 6:27 ` [PATCH 2/2] gpio: tegra: Delete tegra_gpio_enable/disable() Stephen Warren
2012-02-21 10:44 ` Linus Walleij
2012-02-21 18:54 ` Stephen Warren
2012-02-20 7:39 ` [PATCH 1/2] Documentation/gpio.txt: Explain expected pinctrl interaction Russell King - ARM Linux
2012-02-21 10:41 ` Linus Walleij
2012-02-21 11:06 ` Russell King - ARM Linux
[not found] ` <20120221110618.GJ22562-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2012-02-21 12:40 ` Linus Walleij
2012-02-21 12:44 ` Russell King - ARM Linux
2012-02-21 13:02 ` Russell King - ARM Linux
[not found] ` <20120221124409.GL22562-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2012-02-21 13:08 ` Linus Walleij
2012-02-21 19:14 ` Stephen Warren
2012-02-22 6:01 ` Linus Walleij
2012-02-23 0:45 ` Stephen Warren
2012-02-21 18:50 ` Stephen Warren
2012-02-21 10:46 ` Linus Walleij [this message]
[not found] ` <CACRpkdbPeVBv5VWefDvib5HmGF0K2gT79Mx7g-yviyQj33+Z-w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-12 16:32 ` Grant Likely
2012-03-12 17:19 ` Stephen Warren
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=CACRpkdbPeVBv5VWefDvib5HmGF0K2gT79Mx7g-yviyQj33+Z-w@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=ccross@android.com \
--cc=cjb@laptop.org \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rdunlap@xenotime.net \
--cc=swarren@nvidia.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).