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

2019-06-08 Thread Jonathan Cameron
On Mon, 3 Jun 2019 09:30:40 +0200 H. Nikolaus Schaller wrote: > Hi Jonathan, > sorry again for the long delay. I just now found a little time to summarize > and try to > get the discussion boiled down to the key difference. > > > Am 11.05.2019 um 13:05 schrieb Jonathan Cameron : > > > > On Thu

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

2019-05-11 Thread Roderick Colenbrander
On Fri, May 10, 2019 at 1:57 AM Bastien Nocera wrote: > > On Sun, 2019-04-14 at 09:26 -0700, Roderick Colenbrander wrote: > > > > > We at the time were one of the first to expose acceleration and gyro > > data through /dev/input for DualShock 4 as supported by hid-sony. We > > report acceleration

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

2019-05-11 Thread Jonathan Cameron
On Thu, 9 May 2019 19:02:49 +0200 "H. Nikolaus Schaller" wrote: > > Am 09.05.2019 um 11:09 schrieb H. Nikolaus Schaller : > > > > Hi Jonathan, > >> > >> > >> And how does that work on the common case of a sensor in the lid of a > >> laptop? > >> how do you know what angle the screen is at?

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

2019-05-11 Thread Jonathan Cameron
On Thu, 9 May 2019 11:09:26 +0200 "H. Nikolaus Schaller" wrote: > Hi Jonathan, > sorry for the delayed response, but I have to focus on other topics now. No worries. I have the same 'problem'! Hence nothing yet from my side on an alternative. > > Just some small comments came to my mind to fin

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

2019-05-10 Thread H. Nikolaus Schaller
> Am 10.05.2019 um 11:35 schrieb Bastien Nocera : > > On Fri, 2019-05-10 at 11:33 +0200, H. Nikolaus Schaller wrote: >>> > >> It does through "Input device name:" starting with "iio-bridge:" as >> you can see in the commit message of [RFC v3]: > > This makes it ABI, right? The "Input device

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

2019-05-10 Thread H. Nikolaus Schaller
> Am 10.05.2019 um 10:57 schrieb Bastien Nocera : > > On Mon, 2019-04-22 at 15:20 +0100, Jonathan Cameron wrote: >>> Different goals usually lead to different solution architectures. >> >> Indeed, but in this case we have your proposal which is a subset of >> what >> I am suggesting. One archi

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

2019-05-10 Thread Bastien Nocera
On Fri, 2019-05-10 at 11:33 +0200, H. Nikolaus Schaller wrote: > > > It does through "Input device name:" starting with "iio-bridge:" as > you can see in the commit message of [RFC v3]: This makes it ABI, right? Big fat warnings around the code that declares it would be appreciated.

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

2019-05-10 Thread Bastien Nocera
On Sun, 2019-04-14 at 09:26 -0700, Roderick Colenbrander wrote: > > We at the time were one of the first to expose acceleration and gyro > data through /dev/input for DualShock 4 as supported by hid-sony. We > report acceleration in 'g' and angular velocity in 'degree / s'. We > set the resolutio

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

2019-05-10 Thread Bastien Nocera
On Mon, 2019-04-22 at 15:20 +0100, Jonathan Cameron wrote: > > Different goals usually lead to different solution architectures. > > Indeed, but in this case we have your proposal which is a subset of > what > I am suggesting. One architecture can fulfil both requirements. > > I'll leave it for

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

2019-05-09 Thread H. Nikolaus Schaller
> Am 09.05.2019 um 11:09 schrieb H. Nikolaus Schaller : > > Hi Jonathan, >> >> >> And how does that work on the common case of a sensor in the lid of a laptop? >> how do you know what angle the screen is at? > > Well, I am not aware of laptops where the sensor is in the lid because I am >

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

2019-05-09 Thread H. Nikolaus Schaller
Hi Jonathan, sorry for the delayed response, but I have to focus on other topics now. Just some small comments came to my mind to finish the discussion, mainly on the accelerometer in the lid case (see inline below). BR and thanks, Nikolaus > Am 22.04.2019 um 16:20 schrieb Jonathan Cameron : >

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

2019-04-22 Thread Jonathan Cameron
On Mon, 15 Apr 2019 23:04:15 +0200 H. Nikolaus Schaller wrote: > Hi Jonathan, > we seem to have opposite goals and therefore quite different ideas what the > right > solution is. Yup :) Yikes this email has gotten complex. Hopefully I haven't lost track of the various points below. > > I co

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

2019-04-14 Thread Roderick Colenbrander
Hi Jonathan and Nikolaus, I would like to jump into this discussion a bit as well. Might be slightly off topic or not... I'm not too familiar with the details of IIO, but as Sony we do report accelerometer / gyroscope data through /dev/input for our DualShock devices through hid-sony. This is amon

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

2019-04-14 Thread Jonathan Cameron
On Mon, 8 Apr 2019 15:15:56 +0200 H. Nikolaus Schaller wrote: > Hi Jonathan, > > > Am 07.04.2019 um 14:30 schrieb Jonathan Cameron : > > > > On Sun, 31 Mar 2019 12:09:46 +0200 > > "H. Nikolaus Schaller" wrote: > > > > Hi Nikolaus, > > > > I'm probably going to repeat a few things I sent for

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

2019-04-07 Thread Jonathan Cameron
On Sun, 31 Mar 2019 12:09:46 +0200 "H. Nikolaus Schaller" wrote: Hi Nikolaus, I'm probably going to repeat a few things I sent for v1 as the audience has expanded somewhat! Good to see this moving forwards though as there has been at least some demand for it going way back to the early days of

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

2019-03-31 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 a