linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* EV_MSC/MSC_SCAN Behaviour
@ 2010-05-12 19:53 Arce, Abraham
  2010-05-13  7:54 ` Dmitry Torokhov
  0 siblings, 1 reply; 2+ messages in thread
From: Arce, Abraham @ 2010-05-12 19:53 UTC (permalink / raw)
  To: linux-input@vger.kernel.org

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?

Best Regards
Abraham

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: EV_MSC/MSC_SCAN Behaviour
  2010-05-12 19:53 EV_MSC/MSC_SCAN Behaviour Arce, Abraham
@ 2010-05-13  7:54 ` Dmitry Torokhov
  0 siblings, 0 replies; 2+ messages in thread
From: Dmitry Torokhov @ 2010-05-13  7:54 UTC (permalink / raw)
  To: Arce, Abraham; +Cc: linux-input@vger.kernel.org

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-05-13  7:54 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-12 19:53 EV_MSC/MSC_SCAN Behaviour Arce, Abraham
2010-05-13  7:54 ` Dmitry Torokhov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).