Intel Integrated Sensor Hub (ISH) Support In Linux 4.9 Kernel

[phoronix]

Phoronix: Intel Integrated Sensor Hub (ISH) Support In Linux 4.9 Kernel

The Intel Integrated Sensor Hub (ISH) is supported in the Linux 4.9 kernel code for benefiting Cherrytrail mobile/convertible/ultrabook hardware and newer...

http://www.phoronix.com/scan.php?page=news_item&px=Intel-ISH-HID-Linux-4.9

[bregma]

Nice. Now if only there were an IIO-evdev bridge so there was a sane userspace interface, we might see some actual useful software developed for our devices.

[cj.wijtmans]

Nice. Now if only there were an IIO-evdev bridge so there was a sane userspace interface, we might see some actual useful software developed for our devices.

my libinput already replaced evdev...

[StefanBruens]

Nice. Now if only there were an IIO-evdev bridge so there was a sane userspace interface, we might see some actual useful software developed for our devices.

https://github.com/hadess/iio-sensor-proxy

Provides a DBUS interface. DBUS is a better match here, as the number of subscribers is not limited, whereas an input device can only be opened once.

[andrei_me]

Michael Typo: lenogo instead of lenovo

[bregma]

my libinput already replaced evdev...

Evdev is the kernel API that libinput is built on top of. It's in no way a replacement for it, just a very useful application of it.

[bregma]

DBUS is a better match here, as the number of subscribers is not limited, whereas an input device can only be opened once.

Well, I'm not entirely sure the sheer volume of data flowing through the D-Bus is going to cut the mustard, unless D-Bus is moved into the kernel. ALso, it would require applications and toolkits to handle some input sources completely different from others. It would make much much more sense to route the sensor input through evdev (and libinput, see above) and hance through the same routing as all the other input that needs to get processed. That way would also, for example, allow things like the screen position sensor and ambient light detection to be associated with a physical display, the way touchscreens are.

At any rate, the IIO interface is horridly wretched to use from a userspace point of view. It's like it was designed by a kernel hacker who has never written any userland code in his life. The fact that these devices have been around and supported through IIO for years and there's almost no software built on it is ample proof. Even in Android the 9DOF devices have custom evdev interfaces instead.