From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib
Date: Wed, 20 Apr 2011 22:26:14 +0800 [thread overview]
Message-ID: <BANLkTint6DGgosVkjK-sveyA9SL9WVS4Mg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimqpP2k1tBvRL0BXs9E-Q=3bh0C7Q@mail.gmail.com>
On Tue, Apr 19, 2011 at 4:51 PM, Kyungmin Park <kmpark@infradead.org> wrote:
>>
>> Leaving aside the current input/output and on/off bits I would go for
>> being able to do
>>
>> ? ? ? ?gpio_get_property(gpio, GPIO_BIAS, GPIO_BIAS_WHATEVER);
>> ? ? ? ?gpio_set_property(gpio, GPIO_BIAS, GPIO_BIAS_WHATEVER_ELSE);
>
> One more consideration, not mentioned previous time, is that pin
> configuration for power down mode.
> Samsung SoCs has retention GPIO configurations at sleep (suspend)
> mode. and restore it at resume time.
> it's need to reduce power and proper operation after suspend.
>
I have a little confusion. In ARM SoC, a lot of pins are used as
multi-functions.
Before suspend, it may be configured as some function that isn't GPIO.
Is it a goal
that avoid declaring gpio_request() for suspend and updating the setting of pin?
Linus,
Are these two patches are post in mailing list? I can't find your
second patch in this
patch series?
next prev parent reply other threads:[~2011-04-20 14:26 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 21:37 [PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib Linus Walleij
2011-04-17 21:48 ` Alan Cox
2011-04-17 21:58 ` Linus Walleij
2011-04-17 22:03 ` Alan Cox
2011-04-18 0:09 ` Kyungmin Park
2011-04-18 7:17 ` Kurt Van Dijck
2011-04-18 8:04 ` Ben Nizette
2011-04-18 8:19 ` Alan Cox
2011-04-18 8:50 ` Ben Nizette
2011-04-18 11:59 ` Mark Brown
2011-04-18 22:16 ` Ben Nizette
2011-04-18 22:31 ` Mark Brown
2011-04-19 4:50 ` Ben Nizette
2011-04-20 12:11 ` Linus Walleij
2011-04-18 12:26 ` Alan Cox
2011-04-18 22:26 ` Ben Nizette
2011-04-19 8:38 ` Alan Cox
2011-04-19 8:51 ` Kyungmin Park
2011-04-20 12:32 ` Linus Walleij
2011-04-20 12:38 ` Kyungmin Park
2011-04-20 14:54 ` Alan Cox
2011-04-20 14:26 ` Haojian Zhuang [this message]
2011-04-20 14:40 ` Kyungmin Park
2011-04-20 15:04 ` Haojian Zhuang
2011-04-20 15:17 ` Linus Walleij
2011-04-20 15:32 ` Alan Cox
2011-04-20 15:45 ` Linus Walleij
2011-04-27 21:55 ` Russell King - ARM Linux
2011-04-27 22:16 ` H Hartley Sweeten
2011-04-20 15:13 ` Linus Walleij
2011-04-20 15:29 ` Alan Cox
2011-04-20 15:39 ` Linus Walleij
2011-04-20 15:43 ` Alan Cox
2011-04-27 21:58 ` Russell King - ARM Linux
2011-04-20 0:09 ` Ben Nizette
2011-04-20 9:45 ` Alan Cox
2011-04-20 12:38 ` Linus Walleij
2011-04-20 14:55 ` Alan Cox
2011-04-20 12:21 ` Linus Walleij
2011-04-20 23:32 ` Ben Nizette
2011-04-21 6:48 ` Linus Walleij
2011-04-23 8:25 ` Ben Nizette
2011-04-21 0:29 ` Ben Nizette
2011-04-20 12:19 ` Linus Walleij
2011-04-20 12:22 ` Alan Cox
2011-04-20 12:04 ` Linus Walleij
2011-04-20 23:24 ` Ben Nizette
2011-04-21 15:39 ` Stijn Devriendt
2011-04-22 11:36 ` Linus Walleij
2011-04-22 11:56 ` Alan Cox
2011-04-23 8:35 ` Ben Nizette
2011-04-25 18:52 ` Rohit Vaswani
2011-04-26 7:48 ` Linus Walleij
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=BANLkTint6DGgosVkjK-sveyA9SL9WVS4Mg@mail.gmail.com \
--to=haojian.zhuang@gmail.com \
--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).