Re: [RFC v3] iio: input-bridge: optionally bridge iio acceleometers to create a /dev/input interface

2019-05-10 Thread Bastien Nocera
On Tue, 2019-04-16 at 21:33 +0200, H. Nikolaus Schaller wrote: > Hi Bastien, > > > Am 16.04.2019 um 18:04 schrieb Bastien Nocera : > > This can be done in user-space, reading the data from the IIO driver, > > and using uinput to feed it back. Why is doing this at the kernel level > > better? > >

Re: [RFC v3] iio: input-bridge: optionally bridge iio acceleometers to create a /dev/input interface

2019-04-16 Thread H. Nikolaus Schaller
Hi Bastien, > Am 16.04.2019 um 18:04 schrieb Bastien Nocera : > > Having written a "bridge" myself (I called it a "proxy"[1]), I have a > few comments. > > [1]: https://github.com/hadess/iio-sensor-proxy Nice work! > > Let's start with the easy ones ;) there's a typo in the subject line. >

Re: [RFC v3] iio: input-bridge: optionally bridge iio acceleometers to create a /dev/input interface

2019-04-16 Thread Bastien Nocera
Having written a "bridge" myself (I called it a "proxy"[1]), I have a few comments. [1]: https://github.com/hadess/iio-sensor-proxy Let's start with the easy ones ;) there's a typo in the subject line. The subject line also says "optionally" but there doesn't seem to be any ways to disable the

[RFC v3] iio: input-bridge: optionally bridge iio acceleometers to create a /dev/input interface

2019-04-15 Thread H. Nikolaus Schaller
Some user spaces (e.g. some Android devices) use /dev/input/event* for handling the 3D position of the device with respect to the center of gravity (earth). This can be used for gaming input, auto-rotation of screens etc. This interface should be the standard for such use cases because it is an