[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51E686C1.8020801@ti.com>
Date: Wed, 17 Jul 2013 14:57:53 +0300
From: Roger Quadros <rogerq@...com>
To: Grygorii Strashko <grygorii.strashko@...com>
CC: Tony Lindgren <tony@...mide.com>,
Kevin Hilman <khilman@...aro.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-omap@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<devicetree-discuss@...ts.ozlabs.org>,
Linus Walleij <linus.walleij@...aro.org>,
Stephen Warren <swarren@...dotorg.org>
Subject: Re: [PATCH 0/3] ARM: OMAP2+: omap_device: add dynamic pinctrl handling
Hi Grygorii,
On 07/17/2013 02:41 PM, Grygorii Strashko wrote:
> Hi Tony, Kevin
>
> This patch series introduces dynamic pinctrl handling in OMAP device framework
> in the same way as it was before switching to DT.
> This allow OMAP devices driver's developers to simply add dynamic pinctrl
> handling for "default", "active", "idle", "sleep" PIN states in their drivers
> by modifying DT definitions only - no modifications in drivers code are not needed.
>
Overall I like the idea but can we make a provision for device drivers to override
this default pin state handling?
The OMAP EHCI driver is one such special case where the wakeup mechanism is tied to pinctrl states
as it uses IO daisy chaining to implement wakeup.
So depending on whether wakeup needs to be enabled or not I must be able to chose whether
I put the pin in just "sleep" state or "sleep with wakeup" state.
cheers,
-roger
--
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/
Powered by blists - more mailing lists