From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] Documentation/gpio.txt: Explain expected pinctrl interaction
Date: Mon, 20 Feb 2012 07:39:41 +0000 [thread overview]
Message-ID: <20120220073941.GC22562@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1329719263-18971-1-git-send-email-swarren@nvidia.com>
On Sun, Feb 19, 2012 at 11:27:42PM -0700, Stephen Warren 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.
So what if you need to have the pin as a GPIO, manipulate it as a GPIO,
and then hand it off to a special function, and then take it back as
a GPIO before you shut the special function down ?
next prev parent reply other threads:[~2012-02-20 7:39 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 ` Russell King - ARM Linux [this message]
2012-02-21 10:41 ` [PATCH 1/2] Documentation/gpio.txt: Explain expected pinctrl interaction Linus Walleij
2012-02-21 11:06 ` Russell King - ARM Linux
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
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
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=20120220073941.GC22562@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).