linux-kernel - Re: [RFC] ARM: OMAP2+: omap_device: add pinctrl handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 27 Jun 2013 19:04:41 +0300
From:	Grygorii Strashko <grygorii.strashko@...com>
To:	Tony Lindgren <tony@...mide.com>
CC:	Linus Walleij <linus.walleij@...aro.org>,
	Kevin Hilman <khilman@...aro.org>,
	Hebbar Gururaja <gururaja.hebbar@...com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Linux-OMAP <linux-omap@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Stephen Warren <swarren@...dotorg.org>
Subject: Re: [RFC] ARM: OMAP2+: omap_device: add pinctrl handling

On 06/27/2013 05:45 PM, Tony Lindgren wrote:
> * Grygorii Strashko <grygorii.strashko@...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?
  Confirm )
>
> If your hardware does not have specific off mode bits, then
> I can understand that you may need one mor state "off".
>
> Regards,
>
> Tony
>

Regards,
-grygorii
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/