From: Laxman Dewangan <ldewangan@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"linus.walleij@stericsson.com" <linus.walleij@stericsson.com>,
"jedu@slimlogic.co.uk" <jedu@slimlogic.co.uk>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH V1] gpio: tps65910: Add sleep control support
Date: Wed, 1 Feb 2012 12:06:29 +0530 [thread overview]
Message-ID: <4F28DD6D.9030606@nvidia.com> (raw)
In-Reply-To: <CACRpkdZ-1VBkZN71eFqaxVi5dakP4Dt3yXLa9TTdrKE=dGq__w@mail.gmail.com>
On Wednesday 01 February 2012 03:01 AM, Linus Walleij wrote:
> On Tue, Jan 31, 2012 at 9:45 AM, Laxman Dewangan<ldewangan@nvidia.com> wrote:
>
>> The device tps65910/tps65911 supports the sleep
>> functionality in some of gpios. If gpio is configured
>> in output mode and sleep is enabled then during device
>> sleep state, the output of gpio becomes LOW regardless
>> of non-sleep output value.
>> Such gpio can be used to control regulator switch such
>> that output of regulator is off in device sleep state.
>>
>> Signed-off-by: Laxman Dewangan<ldewangan@nvidia.com>
> Strictly speaking this is pin control business, but since it is already
> doing other stuff like this from platform data why not...
>
> Comments:
>
Thanks for review. I have taken care of all your comments and will send
another version with these changes.
prev parent reply other threads:[~2012-02-01 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 8:45 Laxman Dewangan
2012-01-31 21:31 ` Linus Walleij
2012-02-01 6:36 ` Laxman Dewangan [this message]
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=4F28DD6D.9030606@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=jedu@slimlogic.co.uk \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sameo@linux.intel.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
Powered by JetHome