From: Tony Lindgren <tony@atomide.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
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: Thu, 27 Jun 2013 07:45:35 -0700 [thread overview]
Message-ID: <20130627144535.GK5523@atomide.com> (raw)
In-Reply-To: <51CC45D3.2000305@ti.com>
* Grygorii Strashko <grygorii.strashko@ti.com> [130627 07:12]:
>
> As you can see, from 12 pins only 3 pins need to be reconfigured
> while switching from "active"->"idle" states and back (and as I
> mentioned above for OMAP "idle" == "sleep" now).
>
> Regarding "OFF" state:
> OMAP mux HW defines special state for unused pins which is selected
> by default after reset and need to be selected when device isn't
> used, for example:
> _MUXMODE - Functional multiplexing selection for pad
> 0x0: Select usbb1_hsic_data
> 0x3: Select gpio_96
> 0x7: Select safe_mode <<--- pin unused
The off mode bits can be enabled continuously, the mux hardware
automatically sets them. So sounds like you don't need any
separate "idle" "sleep" and "off" states, the following should
do:
"default" (or "static") static pins that don't need to be touched
after consumer driver probe
"active" dynamic pins that are not a subset of
"default" needed for runtime; these pins
are the same as "idle" below, but with
different muxing or pinconf device
runtime
"idle" dynamic pins that are not a subset of
"default" needed for various idle modes;
these pins are the same as "active" above,
but with different muxing or pinconf for
various idle states
Can you please confirm that these named modes are enough for
your needs?
If your hardware does not have specific off mode bits, then
I can understand that you may need one mor state "off".
Regards,
Tony
next prev parent reply other threads:[~2013-06-27 14:45 UTC|newest]
Thread overview: 16+ 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-24 12:06 ` Linus Walleij
2013-06-25 6:58 ` Tony Lindgren
2013-06-26 13:20 ` Grygorii Strashko
2013-06-26 14:36 ` Grygorii Strashko
2013-06-26 19:31 ` Linus Walleij
2013-06-27 7:30 ` Tony Lindgren
2013-06-27 14:01 ` Grygorii Strashko
2013-06-27 14:45 ` Tony Lindgren [this message]
2013-06-27 16:04 ` Grygorii Strashko
2013-07-10 20:42 ` Linus Walleij
2013-07-10 20:36 ` Linus Walleij
2013-07-11 6:17 ` Tony Lindgren
2013-07-12 15:36 ` Grygorii Strashko
2013-07-22 21:00 ` Linus Walleij
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=20130627144535.GK5523@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox