Hello Dimitry, On Sunday 03 April 2011 06:23:05 Dmitry Torokhov wrote: > On Sat, Apr 02, 2011 at 10:31:53AM +0200, Alexander Stein wrote: > > Hello Dimitry, > > > > On Wednesday 16 March 2011 07:36:18 Dmitry Torokhov wrote: > > > On Tue, Mar 15, 2011 at 02:13:49PM +0100, Alexander Stein wrote: > > > > On Friday 25 February 2011, 14:29:18 Alexander Stein wrote: > > > > > This patch adds a generic driver for slide switches connected to > > > > > GPIO pins of a system. It requires gpiolib and generic hardware > > > > > irqs. > > > > > > Hm, can't it be merged with gpio_keys? Just add the 'value' to the > > > gpio_keys_button structure that would be valid for EV_ABS (or even > > > EV_REL) types. Debouncing should filter out jittery events... > > > > Sorry, for no answer long time. > > I just tried merging both. The problem i noticed is that the PGIO > > interrupts are independable and each GPIO will generate an event, which > > is wrong. Assume the switch state change from position 2 to 1 it will > > actually generate lots of interrupts: e.g. 2, 1, 2, 1. > > Depending from the order of such interrupts the last event shows a > > possible wrong position. > > However at some point the output should stabilize. Does not setting > appropriate debouncing interval help here? Well, a debounce interval will prevent to get events for position 2, 1, 2, 1 (from the example above). You will get only 2 and 1. The debounce will only decrease the amount of events for _each_ GPIO interrupt. It will not prevent GPIO interrupts from different pins while moving the switch one position. Alexander -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
