public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Barry Song <21cnbao@gmail.com>,
	Shawn Guo <shawn.guo@freescale.com>,
	Linus Walleij <linus.walleij@stericsson.com>,
	linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>,
	Linaro Dev <linaro-dev@lists.linaro.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	David Brown <davidb@codeaurora.org>,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH 2/2] pinctrl: add a generic control interface
Date: Fri, 21 Oct 2011 13:55:44 +0100	[thread overview]
Message-ID: <20111021125544.GF4080@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACRpkdaZQ12W2M9m=vvQ=w6vRppgsZdphm4ftmx6uFAX2HDkog@mail.gmail.com>

On Fri, Oct 21, 2011 at 02:51:46PM +0200, Linus Walleij wrote:
> On Fri, Oct 21, 2011 at 2:30 PM, Mark Brown

> > To repeat once more: this is *not* an on/off control, this is a control
> > selecting the voltage domain a pin is referenced to.

> Sorry, slow learner. So I'll add:
> PIN_CONFIG_ENABLE_POWER
> PIN_CONFIG_DISABLE_POWER

> With the semantics of enabling/disabling the power
> supply for the pin logic. Correct now?

No, like I keep saying it's nothing to do with enabling or disabling
power.  It's about selecting between multiple reference domains.  For
example, choosing between the DBVDD1 and DBVDD2 domains.

  reply	other threads:[~2011-10-21 12:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 16:21 [PATCH 2/2] pinctrl: add a generic control interface Linus Walleij
2011-10-19 23:04 ` Stephen Warren
2011-10-20  2:45   ` Shawn Guo
2011-10-20 13:44     ` Linus Walleij
2011-10-20 18:41       ` Stephen Warren
2011-10-20 13:46     ` Linus Walleij
2011-10-20 10:24   ` Linus Walleij
2011-10-20 18:46     ` Stephen Warren
2011-10-20  2:31 ` Shawn Guo
2011-10-20  9:17   ` Barry Song
2011-10-20 13:10     ` Shawn Guo
2011-10-20 14:18       ` Linus Walleij
2011-10-23  8:51         ` Shawn Guo
2011-10-25  4:49           ` Stephen Warren
2011-10-20 14:04     ` Linus Walleij
2011-10-20 14:18       ` Mark Brown
2011-10-20 14:43         ` Linus Walleij
2011-10-20 15:42           ` Mark Brown
2011-10-21 12:28             ` Linus Walleij
2011-10-21 12:30               ` Mark Brown
2011-10-21 12:51                 ` Linus Walleij
2011-10-21 12:55                   ` Mark Brown [this message]
2011-10-21 12:57                     ` Linus Walleij
2011-10-21 15:24                       ` Mark Brown
2011-10-20 17:26   ` Stephen Warren
2011-10-23  8:25     ` Shawn Guo
2011-10-25  4:43       ` 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=20111021125544.GF4080@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=21cnbao@gmail.com \
    --cc=davidb@codeaurora.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawn.guo@freescale.com \
    --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