linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: linus.walleij@linaro.org, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] pinctrl: Add support for additional dynamic states
Date: Mon, 29 Jul 2013 02:05:24 -0700	[thread overview]
Message-ID: <20130729090524.GY7656@atomide.com> (raw)
In-Reply-To: <51E98AEC.5000802@wwwdotorg.org>

* Stephen Warren <swarren@wwwdotorg.org> [130719 11:59]:
> On 07/19/2013 01:29 AM, Tony Lindgren wrote:
> > 
> > I'd vote for keeping the existing behaviour with pinctrl_select_state()
> > when no active state is defined.
> 
> Yes, I think that will work, since the active state cannot exist before
> this new scheme is in place.

Right.
 
> But, this needs to be very clearly spell out in the DT binding
> documentation: If you have states default/idle/sleep, they're complete
> alternatives, whereas if you have states default/active/idle/sleep, the
> latter 3 are alternatives that build on top of the first. I foresee mass
> confusion, but perhaps I'm being pessimistic.

I'm hoping we can automate the runtime PM handling with default/active/idle
completely from the consumer driver point of view. And then when that's
working, we can probably deprecate any runtime PM related handling using
pinctr_select_state() and print warnings. And we can also improve the
documentation so no new users will use the default/idle/sleep for runtime
PM unless they really want to.

Regards,

Tony

  reply	other threads:[~2013-07-29  9:05 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16  9:05 [PATCH 0/4] improved support for runtime muxing for pinctrl Tony Lindgren
2013-07-16  9:05 ` [PATCH 1/4] pinctrl: Remove duplicate code in pinctrl_pm_select_state functions Tony Lindgren
2013-07-16 13:15   ` Grygorii Strashko
2013-07-16 13:41     ` Tony Lindgren
2013-07-16 14:25       ` Grygorii Strashko
2013-07-17  6:31         ` Tony Lindgren
2013-07-16  9:05 ` [PATCH 2/4] pinctrl: Allow pinctrl to have multiple active states Tony Lindgren
2013-07-17 20:55   ` Stephen Warren
2013-07-16  9:05 ` [PATCH 3/4] pinctrl: Add support for additional dynamic states Tony Lindgren
2013-07-16  9:35   ` Felipe Balbi
2013-07-16 12:06     ` Tony Lindgren
2013-07-17 21:14   ` Stephen Warren
2013-07-18  7:25     ` Tony Lindgren
2013-07-18 10:53       ` Tony Lindgren
2013-07-18 19:21       ` Stephen Warren
2013-07-19  7:29         ` Tony Lindgren
2013-07-19 18:52           ` Stephen Warren
2013-07-29  9:05             ` Tony Lindgren [this message]
2013-07-29 22:01               ` Stephen Warren
2013-08-14 16:41                 ` Linus Walleij
2013-07-17 21:23   ` Stephen Warren
2013-07-18  7:36     ` Tony Lindgren
2013-07-18 19:26       ` Stephen Warren
2013-07-19  7:39         ` Tony Lindgren
2013-07-19 10:29           ` Grygorii Strashko
2013-07-19 19:03             ` Stephen Warren
2013-07-22 23:15               ` Linus Walleij
2013-07-29  9:08               ` Tony Lindgren
2013-07-19 18:58           ` Stephen Warren
2013-07-29  9:21             ` Tony Lindgren
2013-07-29 22:08               ` Stephen Warren
2013-07-22 23:07   ` Linus Walleij
2013-07-29  9:31     ` Tony Lindgren
2013-07-16  9:05 ` [PATCH 4/4] drivers: Add pinctrl handling for dynamic pin states Tony Lindgren
2013-07-17 21:21   ` Stephen Warren
2013-07-18  7:50     ` Tony Lindgren
2013-07-18 13:48       ` Tony Lindgren
2013-07-16  9:14 ` [PATCH 0/4] improved support for runtime muxing for pinctrl Tony Lindgren
2013-07-17 11:49 ` Grygorii Strashko
  -- strict thread matches above, loose matches on Subject: below --
2013-07-18 15:15 [PATCHv2 " Tony Lindgren
2013-07-18 15:15 ` [PATCH 3/4] pinctrl: Add support for additional dynamic states 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=20130729090524.GY7656@atomide.com \
    --to=tony@atomide.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=swarren@wwwdotorg.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).