On Mon, May 17, 2010 at 1:02 PM, <felipe.balbi@xxxxxxxxx> wrote: > From: Felipe Balbi <felipe.balbi@xxxxxxxxx> > > stop using the omap-specific implementations for gpio > debouncing now that gpiolib provides its own support. hmm, this gives me: [ 0.000000] WARNING: at drivers/gpio/gpiolib.c:104 gpio_ensure_requested+0x50/0xcc() [ 0.000000] autorequest GPIO-96 [ 0.000000] Modules linked in: [ 0.000000] [<c00302bc>] (unwind_backtrace+0x0/0xec) from [<c00510dc>] (warn_slowpath_common+0x4c/0x64) [ 0.000000] [<c00510dc>] (warn_slowpath_common+0x4c/0x64) from [<c0051174>] (warn_slowpath_fmt+0x2c/0x3) [ 0.000000] [<c0051174>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0166c2c>] (gpio_ensure_requested+0x50/0x) [ 0.000000] [<c0166c2c>] (gpio_ensure_requested+0x50/0xcc) from [<c0166d14>] (gpio_set_debounce+0x6c/0x) [ 0.000000] [<c0166d14>] (gpio_set_debounce+0x6c/0xb0) from [<c000ee84>] (omap3pandora_init+0x94/0xcc) [ 0.000000] [<c000ee84>] (omap3pandora_init+0x94/0xcc) from [<c000b300>] (customize_machine+0x18/0x24) ..and later gpio-keys is unable to request the same GPIO because of above autorequest. So how is this supposed to be used here, should I request all GPIOs I want to have debouncing on, setup debounce time and release them for gpio-keys to take? Or should I wait for this to get supported in gpio-keys? -- 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
