Re: Handling of non-positional data through evdev

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

 



Hi Bastien,

Thanks for providing this suggestion. I can see this approach work for
situations like screen rotation on tablets. The device I'm involved
with is an input device, which needs a high poll rate for acceleration
/ velocity and needs to be paired with the button / axes data. Evdev
would be most appropriate.

Thanks,
Roderick

On Tue, Mar 15, 2016 at 3:59 PM, Bastien Nocera <hadess@xxxxxxxxxx> wrote:
> On Tue, 2016-03-15 at 12:26 -0700, Roderick Colenbrander wrote:
>> Hi all,
>>
>> I'm working on a device driver for an input device, which has both
>> directional axes in addition to sensors (accelerometer and gyro). I'm
>> trying to figure out how to map these axes properly, but I'm
>> stumbling
>> on some road blocks.
>
> Depending on what your device is, you might be looking for the IIO sub-
> system instead, which hosts most of the sensor-type drivers.
>
> iio-sensor-proxy is one of the daemon that can consume data from it
> (even if somewhat unelegantly these days).
>
> Cheers
--
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