Thread (3 messages) 3 messages, 2 authors, 2011-06-20
DORMANTno replies
Revisions (5)
  1. v2 [diff vs current]
  2. v2 [diff vs current]
  3. v2 [diff vs current]
  4. v2 current
  5. v3 [diff vs current]

[PATCH v2 00/18] GPIO: OMAP: Driver Cleanup and Fixes

From: DebBarma, Tarun Kanti <hidden>
Date: 2011-06-20 20:00:25
Also in: linux-omap

[...]
A quick test of this series on 3430/n900 shows that it prevents PER
retention.  I see CM_FCLKEN_PER=0000c000 (debounce clock for GPIO banks
3 & 4 are still enabled.)

Can you retest with debounce enabled on one of the GPIOs for one of your
platforms?
With one of the module debounce clock enabled it doesn't go to retention.
Later I disabled all modules debounce clock. It doesn't to retention either.
So this is same as your observation. I am surprised what has happened now.
The only thing I could recollect is few patches to solve LDO and
OMAP1 issues while testing before posting. I will investigate further.
--
Tarun
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