Re: [PATCH 2/2] gpio: omap: compute debounce-time from actual debounce-clock rate

2017-04-20 Thread David Rivshin
On Fri, 17 Mar 2017 19:06:47 -0500 Grygorii Strashko wrote: > CC: Tero Gentle ping. Any thoughts on this? Is there anything I should investigate, or other information you'd like me to provide? > On 03/17/2017 06:14 PM, David Rivshin wrote: > > On Fri, 17 Mar 2017 14:43:02 -0500 > > Grygorii S

Re: [PATCH 2/2] gpio: omap: compute debounce-time from actual debounce-clock rate

2017-03-17 Thread Grygorii Strashko
CC: Tero On 03/17/2017 06:14 PM, David Rivshin wrote: On Fri, 17 Mar 2017 14:43:02 -0500 Grygorii Strashko wrote: On 03/16/2017 07:57 PM, David Rivshin wrote: From: David Rivshin omap2_set_gpio_debounce() assumes the debounce clock runs at 32768Hz, leading to 31us granularity. In reality t

Re: [PATCH 2/2] gpio: omap: compute debounce-time from actual debounce-clock rate

2017-03-17 Thread David Rivshin
On Fri, 17 Mar 2017 14:43:02 -0500 Grygorii Strashko wrote: > On 03/16/2017 07:57 PM, David Rivshin wrote: > > From: David Rivshin > > > > omap2_set_gpio_debounce() assumes the debounce clock runs at 32768Hz, > > leading to 31us granularity. In reality the debounce clock (which > > is provided

[PATCH 2/2] gpio: omap: compute debounce-time from actual debounce-clock rate

2017-03-16 Thread David Rivshin
From: David Rivshin omap2_set_gpio_debounce() assumes the debounce clock runs at 32768Hz, leading to 31us granularity. In reality the debounce clock (which is provided by other modules) could be at different rate, leading to an incorrect computation of the number of debounce clock cycles for GPIO