Thread (1 message) 1 message, 1 author, 2011-05-26
DORMANTno replies

[PATCH 02/15] OMAP2PLUS: GPIO: Fix non-wakeup GPIO and rev_ids

From: Kevin Hilman <hidden>
Date: 2011-05-26 18:32:39
Also in: linux-omap

"Varadarajan, Charulatha" [off-list ref] writes:
Kevin,

On Thu, May 26, 2011 at 12:15, Kevin Hilman [off-list ref] wrote:
quoted
"Varadarajan, Charulatha" [off-list ref] writes:
quoted
On Thu, May 26, 2011 at 03:04, Kevin Hilman [off-list ref] wrote:
quoted
Tarun Kanti DebBarma [off-list ref] writes:
quoted
From: Charulatha V <redacted>

Non-wakeup GPIOs are available only in OMAP2420 and OMAP3430. But
the GPIO driver initializes the non-wakeup GPIO bits for OMAP24xx
(bothe OMAP 2420 and 2430) & not for OMAP3 which is incorrect.
Can you cite the documentation you're using for the OMAP3 non-wakeup
GPIOs?
I am referring to Table 25-5. GPIO Channel Description at page no 3354
OMAP3430 public TRM Version P.
Based on how I understand that, those non-wakeup GPIOs are non-wakeup
because they're not actually mapped anywhere, and not available on
external pins. ?Therefore, they should not need any special case
handling for this triggering workaround.
Okay. Thanks for clarifying. I will not  do this for OMAP3. The special case
would be only for OMAP2420 against the current code which is handling
for OMAP24xx.
Great, thanks.

Kevin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help