From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: letux-kernel@openphoenux.org, kernel@pyra-handheld.com,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: [RFC 0/4] iio-input-bridge so that accelerometers which only have an iio driver can still present evdev input events
Date: Mon, 18 Mar 2019 21:39:30 +0100 [thread overview]
Message-ID: <cover.1552941573.git.hns@goldelico.com> (raw)
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
next reply other threads:[~2019-03-18 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 20:39 H. Nikolaus Schaller [this message]
2019-03-18 20:39 ` [RFC 1/4] iio: input-bridge: optionally bridge iio acceleometers to create a /dev/input H. Nikolaus Schaller
2019-03-18 20:39 ` [RFC 2/4] iio: input-bridge: add iio-input-bridge to Makefile H. Nikolaus Schaller
2019-03-18 20:39 ` [RFC 3/4] iio: input-bridge: add IIO_INPUT_BRIDGE kernel config option H. Nikolaus Schaller
2019-03-18 20:39 ` [RFC 4/4] iio: input-bridge: make the iio-input-bridge driver called by iio-core H. Nikolaus Schaller
2019-03-24 18:29 ` [RFC 0/4] iio-input-bridge so that accelerometers which only have an iio driver can still present evdev input events Jonathan Cameron
2019-03-28 17:42 ` H. Nikolaus Schaller
2019-03-31 10:09 ` H. Nikolaus Schaller
2019-03-31 11:05 ` Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1552941573.git.hns@goldelico.com \
--to=hns@goldelico.com \
--cc=jic23@kernel.org \
--cc=kernel@pyra-handheld.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=letux-kernel@openphoenux.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).