From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
Kevin Hilman <khilman@linaro.org>,
Hebbar Gururaja <gururaja.hebbar@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: [RFC] ARM: OMAP2+: omap_device: add pinctrl handling
Date: Mon, 24 Jun 2013 23:58:11 -0700 [thread overview]
Message-ID: <20130625065811.GZ5523@atomide.com> (raw)
In-Reply-To: <CACRpkdY=m1b9Lh27+wHP8FQ4SbVZKmAOCGhxe59aP+TcuR9QaA@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [130624 05:13]:
> On Fri, Jun 21, 2013 at 5:03 PM, Grygorii Strashko
> <grygorii.strashko@ti.com> wrote:
>
> > Hence, add pinctrl handling in omap_device core:
> > 1) on PM runtime resume
> > - switch pinctrl state to "default" (todo: "active")
> > 2) on PM runtime suspend
> > - switch pinctrl state to "idle"
> > 3) during system wide suspend
> > - switch pinctrl state to "sleep" or "idle" if omap_device core disables device
> > - switch pinctrl state to "sleep" if device is disabled already
Do you need a separate setting for "idle" and "sleep", or are
they the same?
> > 4) during system wide resume
> > - switch pinctrl state to "default" (todo: "active") if omap_device core has
> > disabled device during suspend
> > - switch pinctrl state to "idle" if device was already disabled before suspend
>
> I don't understand step 4.
>
> I get the creeps about whether the system is runtime suspended
> or runtime resumed when we come to resume proper, so I need
> Kevin to have a look at this.
>
> Apart from that it looks good.
>
> Stephen and Tony are trying to figure out the details of whether "active"
> is necessary or not in a related thread I think.
Yes we should have that sorted out over next few weeks, so let's
just wait a little while on all these dynamic remuxing patches
to avoid churn.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM: OMAP2+: omap_device: add pinctrl handling
Date: Mon, 24 Jun 2013 23:58:11 -0700 [thread overview]
Message-ID: <20130625065811.GZ5523@atomide.com> (raw)
In-Reply-To: <CACRpkdY=m1b9Lh27+wHP8FQ4SbVZKmAOCGhxe59aP+TcuR9QaA@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [130624 05:13]:
> On Fri, Jun 21, 2013 at 5:03 PM, Grygorii Strashko
> <grygorii.strashko@ti.com> wrote:
>
> > Hence, add pinctrl handling in omap_device core:
> > 1) on PM runtime resume
> > - switch pinctrl state to "default" (todo: "active")
> > 2) on PM runtime suspend
> > - switch pinctrl state to "idle"
> > 3) during system wide suspend
> > - switch pinctrl state to "sleep" or "idle" if omap_device core disables device
> > - switch pinctrl state to "sleep" if device is disabled already
Do you need a separate setting for "idle" and "sleep", or are
they the same?
> > 4) during system wide resume
> > - switch pinctrl state to "default" (todo: "active") if omap_device core has
> > disabled device during suspend
> > - switch pinctrl state to "idle" if device was already disabled before suspend
>
> I don't understand step 4.
>
> I get the creeps about whether the system is runtime suspended
> or runtime resumed when we come to resume proper, so I need
> Kevin to have a look at this.
>
> Apart from that it looks good.
>
> Stephen and Tony are trying to figure out the details of whether "active"
> is necessary or not in a related thread I think.
Yes we should have that sorted out over next few weeks, so let's
just wait a little while on all these dynamic remuxing patches
to avoid churn.
Regards,
Tony
next prev parent reply other threads:[~2013-06-25 6:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 15:03 [RFC] ARM: OMAP2+: omap_device: add pinctrl handling Grygorii Strashko
2013-06-21 15:03 ` Grygorii Strashko
2013-06-21 15:03 ` Grygorii Strashko
2013-06-24 12:06 ` Linus Walleij
2013-06-24 12:06 ` Linus Walleij
2013-06-24 12:06 ` Linus Walleij
2013-06-25 6:58 ` Tony Lindgren [this message]
2013-06-25 6:58 ` Tony Lindgren
2013-06-26 13:20 ` Grygorii Strashko
2013-06-26 13:20 ` Grygorii Strashko
2013-06-26 14:36 ` Grygorii Strashko
2013-06-26 14:36 ` Grygorii Strashko
2013-06-26 19:31 ` Linus Walleij
2013-06-26 19:31 ` Linus Walleij
2013-06-27 7:30 ` Tony Lindgren
2013-06-27 7:30 ` Tony Lindgren
2013-06-27 14:01 ` Grygorii Strashko
2013-06-27 14:01 ` Grygorii Strashko
2013-06-27 14:01 ` Grygorii Strashko
2013-06-27 14:45 ` Tony Lindgren
2013-06-27 14:45 ` Tony Lindgren
2013-06-27 16:04 ` Grygorii Strashko
2013-06-27 16:04 ` Grygorii Strashko
2013-06-27 16:04 ` Grygorii Strashko
2013-07-10 20:42 ` Linus Walleij
2013-07-10 20:42 ` Linus Walleij
2013-07-10 20:36 ` Linus Walleij
2013-07-10 20:36 ` Linus Walleij
2013-07-11 6:17 ` Tony Lindgren
2013-07-11 6:17 ` Tony Lindgren
2013-07-12 15:36 ` Grygorii Strashko
2013-07-12 15:36 ` Grygorii Strashko
2013-07-22 21:00 ` Linus Walleij
2013-07-22 21:00 ` Linus Walleij
2013-06-24 17:55 ` Kevin Hilman
2013-06-24 17:55 ` Kevin Hilman
2013-06-24 17:55 ` Kevin Hilman
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=20130625065811.GZ5523@atomide.com \
--to=tony@atomide.com \
--cc=grygorii.strashko@ti.com \
--cc=gururaja.hebbar@ti.com \
--cc=khilman@linaro.org \
--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 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.