lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 18 Mar 2019 21:39:30 +0100
From:   "H. Nikolaus Schaller" <hns@...delico.com>
To:     Jonathan Cameron <jic23@...nel.org>
Cc:     letux-kernel@...nphoenux.org, kernel@...a-handheld.com,
        Hartmut Knaack <knaack.h@....de>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Peter Meerwald-Stadler <pmeerw@...erw.net>,
        linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
        "H. Nikolaus Schaller" <hns@...delico.com>
Subject: [RFC 0/4] iio-input-bridge so that accelerometers which only have an iio driver can still present evdev input events

Some user spaces (e.g. some Android) 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, rotation of screens etc.

This should be the standard because this interface is an abstraction of how
this data is acquired from sensor chips. Sensor chips may be connected through
different interfaces and in different positions. They may also have different
parameters. And, if a chip is replaced by a different one, the values reported
by the device position interface should remain the same.

But nowadays, new accelerometer chips usually just get iio drivers and rarely
an evdev input driver.

Therefore we need something like a protocol stack: input device vs. raw data.
It can be seen as a similar layering like TCP/IP vs. bare Ethernet. Or keyboard
input events vs. raw gpio or raw USB access.

This patch set bridges the gap between raw iio data and the input device abstraction
so that accelerometer measurements can also be presented as X/Y/Z accelerometer
channels (INPUT_PROP_ACCELEROMETER) through /dev/input/event*.


H. Nikolaus Schaller (4):
  iio: input-bridge: optionally bridge iio acceleometers to create a
    /dev/input
  iio: input-bridge: add iio-input-bridge to Makefile
  iio: input-bridge: add IIO_INPUT_BRIDGE kernel config option
  iio: input-bridge: make the iio-input-bridge driver called by iio-core

 drivers/iio/Kconfig                    |   7 +
 drivers/iio/Makefile                   |   1 +
 drivers/iio/industrialio-core.c        |  12 +
 drivers/iio/industrialio-inputbridge.c | 420 +++++++++++++++++++++++++
 drivers/iio/industrialio-inputbridge.h |  28 ++
 5 files changed, 468 insertions(+)
 create mode 100644 drivers/iio/industrialio-inputbridge.c
 create mode 100644 drivers/iio/industrialio-inputbridge.h

-- 
2.19.1

Powered by blists - more mailing lists