Re: Report FSP gesture code through EV_MSC?

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

 



Hi Tai-hwa,

[Noe really cc-ing linux-input...]

On Fri, Aug 20, 2010 at 11:30:14AM +0800, Tai-hwa Liang wrote:
> Hi,
> 
>   Is it okay to use input_event(dev, EV_MSC, MSC_GESTURE, code) to report
> gesture code sent from our FSP?  It looks to me there is no MSC_GESTURE
> user in various kernel input driver so far.
> 
> * gesture code is a feature provided by Sentelic FSP, which converts
>   particular finger movement(single or multiple fingers) into a 8 bit
>   integer.  This supposes to save userland applications some time to
>   parse/process the gesture through multiple abs. coordinates.
> 

While the preferred way is to perform gesture recognition in userland
(where it is easier to adjust to user's preferences and share the code
between all kinds of input devices), for devices that do not report
absolute coordinates, like FSP, it should be OK to use MSC_GESTURE.
Or are you planning to activate absolute mode on your devices?

I think we should define a set of known values for this events so of
there is another driver using these they could use the same values.

Thanks.

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


[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