From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: document the pinctrl PM states
Date: Fri, 14 Jun 2013 09:43:40 -0600 [thread overview]
Message-ID: <51BB3A2C.608@wwwdotorg.org> (raw)
In-Reply-To: <CACRpkdZV7R3MgbuvEMhs24YYv2hK8Kt9Kjmv_cpRQQ1NYviDQg@mail.gmail.com>
On 06/13/2013 02:34 PM, Linus Walleij wrote:
> On Thu, Jun 13, 2013 at 9:39 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 06/11/2013 01:59 PM, Linus Walleij wrote:
>>> From: Linus Walleij <linus.walleij@linaro.org>
>>>
>>> This document snippet tries to be helpful and define the pin
>>> PM states and helpers, and how they should be used to create
>>> some kind of common ontology around this.
>>
>> Oops. I haven't been keeping up well. I propose we hold off on this
>> patch for a short while until the other thread on this topic is finalized.
>
> Isn't it better if I split it?
>
> Most of this doc is about the default/sleep/idle states and
> how that relates to runtime PM, and that seems to be
> uncontroversial.
I would tend to prefer sorting out the issue fully, then documenting it
once. This avoids churn.
I would consider the complete set of standard pinctrl states as an
interface. If we add states, that actually changes the interface even
though it might not affect the definition of any individual states.
Since this also impacts DT which is supposed to be a stable ABI (or at
least evolve in a backwards-compatible fashion), it seems better to get
it right once.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
Stephen Warren <swarren@nvidia.com>,
Kevin Hilman <khilman@linaro.org>,
Tony Lindgren <tony@atomide.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH] pinctrl: document the pinctrl PM states
Date: Fri, 14 Jun 2013 09:43:40 -0600 [thread overview]
Message-ID: <51BB3A2C.608@wwwdotorg.org> (raw)
In-Reply-To: <CACRpkdZV7R3MgbuvEMhs24YYv2hK8Kt9Kjmv_cpRQQ1NYviDQg@mail.gmail.com>
On 06/13/2013 02:34 PM, Linus Walleij wrote:
> On Thu, Jun 13, 2013 at 9:39 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 06/11/2013 01:59 PM, Linus Walleij wrote:
>>> From: Linus Walleij <linus.walleij@linaro.org>
>>>
>>> This document snippet tries to be helpful and define the pin
>>> PM states and helpers, and how they should be used to create
>>> some kind of common ontology around this.
>>
>> Oops. I haven't been keeping up well. I propose we hold off on this
>> patch for a short while until the other thread on this topic is finalized.
>
> Isn't it better if I split it?
>
> Most of this doc is about the default/sleep/idle states and
> how that relates to runtime PM, and that seems to be
> uncontroversial.
I would tend to prefer sorting out the issue fully, then documenting it
once. This avoids churn.
I would consider the complete set of standard pinctrl states as an
interface. If we add states, that actually changes the interface even
though it might not affect the definition of any individual states.
Since this also impacts DT which is supposed to be a stable ABI (or at
least evolve in a backwards-compatible fashion), it seems better to get
it right once.
next prev parent reply other threads:[~2013-06-14 15:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 19:59 [PATCH] pinctrl: document the pinctrl PM states Linus Walleij
2013-06-11 19:59 ` Linus Walleij
2013-06-12 18:37 ` Tony Lindgren
2013-06-12 18:37 ` Tony Lindgren
2013-06-13 19:39 ` Stephen Warren
2013-06-13 19:39 ` Stephen Warren
2013-06-13 20:34 ` Linus Walleij
2013-06-13 20:34 ` Linus Walleij
2013-06-14 15:43 ` Stephen Warren [this message]
2013-06-14 15:43 ` Stephen Warren
2013-06-16 10:17 ` Linus Walleij
2013-06-16 10:17 ` Linus Walleij
2013-06-17 7:20 ` Tony Lindgren
2013-06-17 7:20 ` Tony Lindgren
2013-06-17 15:56 ` Linus Walleij
2013-06-17 15:56 ` Linus Walleij
2013-06-17 18:06 ` Tony Lindgren
2013-06-17 18:06 ` Tony Lindgren
2013-06-17 18:15 ` Rohit Vaswani
2013-06-17 18:15 ` Rohit Vaswani
2013-06-17 16:05 ` Linus Walleij
2013-06-17 16:05 ` Linus Walleij
2013-06-17 18:02 ` Tony Lindgren
2013-06-17 18:02 ` Tony Lindgren
2013-06-19 20:06 ` Stephen Warren
2013-06-19 20:06 ` Stephen Warren
2013-06-24 12:37 ` Linus Walleij
2013-06-24 12:37 ` Linus Walleij
2013-06-25 7:31 ` Tony Lindgren
2013-06-25 7:31 ` Tony Lindgren
2013-06-19 20:02 ` Stephen Warren
2013-06-19 20:02 ` Stephen Warren
2013-06-20 6:38 ` Tony Lindgren
2013-06-20 6:38 ` Tony Lindgren
2013-06-20 19:26 ` Stephen Warren
2013-06-20 19:26 ` Stephen Warren
2013-06-21 6:25 ` Tony Lindgren
2013-06-21 6:25 ` Tony Lindgren
2013-06-21 19:12 ` Stephen Warren
2013-06-21 19:12 ` Stephen Warren
2013-06-24 10:10 ` Tony Lindgren
2013-06-24 10:10 ` Tony Lindgren
2013-06-24 18:09 ` Stephen Warren
2013-06-24 18:09 ` Stephen Warren
2013-06-25 7:38 ` Tony Lindgren
2013-06-25 7:38 ` Tony Lindgren
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=51BB3A2C.608@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.