Re: [PATCH 2/2] input: mt: Document the MT event slot protocol (rev3)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dmitry Torokhov wrote:
> 
> I guess this is where our disconnect lies as when I am looking at the
> event names I view all *_MT_* events as related to the multitouch
> protocol handling.
> 

Yes. It is true that slot control is MT related, but I am looking at this from
the perspective of future expansions like KEY_MT,  KEY_REL, and such, finding a
way to signal to user space which events are handled via slots. If we had
ABS_MT_SLOT, we would most likely get applications which store ABS_MT_SLOT as an
attribute of the slot together with ABS_MT_POSITION_X, ABS_MT_TOUCH_MAJOR, etc,
which is just not right. So the proposal is ABS_SLOT. May we have your verdict,
please. :-)

Henrik
--
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

[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux