Re: [PATCH] gpio: omap: fix debounce time calculation

On 11/12/2015 11:33 AM, Felipe Balbi wrote: Hi, Grygorii Strashko writes: On 11/12/2015 08:09 PM, Felipe Balbi wrote: Hi, Grygorii Strashko writes: On 11/12/2015 07:50 PM, Felipe Balbi wrote: According to TRM, debounce is measured in

Re: [PATCH] gpio: omap: fix debounce time calculation

On 11/12/2015 08:09 PM, Felipe Balbi wrote: Hi, Grygorii Strashko writes: On 11/12/2015 07:50 PM, Felipe Balbi wrote: According to TRM, debounce is measured in periods of the functional clock of the GPIO IP. This means that What TRM? link pls.

Re: [PATCH] gpio: omap: fix debounce time calculation

Hi, Grygorii Strashko writes: > On 11/12/2015 08:09 PM, Felipe Balbi wrote: >> >> Hi, >> >> Grygorii Strashko writes: >>> On 11/12/2015 07:50 PM, Felipe Balbi wrote: According to TRM, debounce is measured in periods of the

[PATCH] gpio: omap: fix debounce time calculation

According to TRM, debounce is measured in periods of the functional clock of the GPIO IP. This means that we should divide by the rate of functional clock. Signed-off-by: Felipe Balbi --- drivers/gpio/gpio-omap.c | 24 +--- 1 file changed, 17 insertions(+), 7

Re: [PATCH] gpio: omap: fix debounce time calculation

On 11/12/2015 07:50 PM, Felipe Balbi wrote: > According to TRM, debounce is measured in periods of > the functional clock of the GPIO IP. This means that What TRM? link pls. http://www.ti.com/lit/ug/spruhl7d/spruhl7d.pdf 28.4.1.24 GPIO_DEBOUNCINGTIME Register (offset = 154h) [reset = 0h] The

Re: [PATCH] gpio: omap: fix debounce time calculation

Hi, Grygorii Strashko writes: > On 11/12/2015 07:50 PM, Felipe Balbi wrote: >> According to TRM, debounce is measured in periods of >> the functional clock of the GPIO IP. This means that > > > What TRM? link pls. > > http://www.ti.com/lit/ug/spruhl7d/spruhl7d.pdf > >