On Wed, May 12, 2010 at 02:53:48PM -0500, Arce, Abraham wrote: > Hi, > > I have searched for documentation regarding this type of event but still not clear about the behaviour. > > input_set_capability(input_dev, EV_MSC, MSC_SCAN); > input_event(input_dev, EV_MSC, MSC_SCAN, code); > > Without enabling it I am able to get events properly reported using evtest in key press, release and kept depressed > > Event: time 946684817.945892, type 1 (Key), code 18 (E), value 2 > > If I enable it then, If I press and release a key no code will be reported > > Event: time 946684836.854248, -------------- Report Sync ------------ > Event: time 946684836.854248, -------------- Report Sync ------------ > > Unless I keep it depressed > > Event: time 946684817.945892, type 1 (Key), code 18 (E), value 2 > > And after releasing the key some other events will get generated > > Event: time 946684817.967559, type 4 (Misc), code 4 (ScanCode), value 24 > Event: time 946684817.967559, -------------- Report Sync ------------ > Event: time 946684817.967559, type 4 (Misc), code 4 (ScanCode), value 32 > Event: time 946684817.967559, -------------- Report Sync ------------ > Event: time 946684817.967590, type 4 (Misc), code 4 (ScanCode), value 40 > Event: time 946684817.967590, -------------- Report Sync ------------ > > Am I missing something? > Probably ;) Just send the code you have so far and we'll figure it out. -- Dmitry -- 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
