Re: [RFC] OMAP3: GPIO: Enable debounce clock only when debounce is enabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Jouni,

On Fri, 12 Sep 2008, Jouni Hogander wrote:

> This patch changes gpio "driver" to enable debounce clock for
> gpio-bank only when debounce is enabled for some gpio in that bank.
> 
> This patch obsoletes "PM: Dynamic GPIO clock handling" patch. Nasty
> side effect is that gpios in per domain aren't capable to generate
> wake-up if per domain is in sleep state. Anyway keeping dbcks enabled
> all the time isn't either good way to workaround this problem. For
> this we need to use iopad wake-up. Currently enabling iopad wakeup
> mechanism for gpio pads is left for bootloader or kernel (depending
> which one does the configuration)

nice resolution to this issue!  Besides Daniel's change, also it would be 
good to rename the "functional" clocks in the clock tree to indicate that 
these are debounce clocks.  Perhaps to GPIOx_DBCLK?


- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux