Thread (13 messages) 13 messages, 5 authors, 2016-03-17

Re: Handling of non-positional data through evdev

From: Roderick Colenbrander <hidden>
Date: 2016-03-16 00:17:57

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 [off-list ref] wrote:
On Tue, 2016-03-15 at 12:26 -0700, Roderick Colenbrander wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help