From: Bastien Nocera <hadess@hadess.net>
To: Roderick Colenbrander <thunderbird2k@gmail.com>,
Jonathan Cameron <jic23@kernel.org>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Eric Piel <eric.piel@tremplin-utc.net>,
linux-input <linux-input@vger.kernel.org>,
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>,
lkml <linux-kernel@vger.kernel.org>,
linux-iio@vger.kernel.org
Subject: Re: [RFC v2] iio: input-bridge: optionally bridge iio acceleometers to create a /dev/input interface
Date: Fri, 10 May 2019 10:57:07 +0200 [thread overview]
Message-ID: <d9f2ee79b8690939f36377990fb6d6fb08e9f0bc.camel@hadess.net> (raw)
In-Reply-To: <CAEc3jaCnHLA9PV5gLiBvHT5y26mwMGSUxa3YCO=c+FYmcszePQ@mail.gmail.com>
On Sun, 2019-04-14 at 09:26 -0700, Roderick Colenbrander wrote:
>
<snip>
> 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 resolution to respectively '1 g' and '1 degree / s'. The range
> we set to the range of the device e.g. for DS4 -4g to +4g for
> acceleration. I need to check though what coordinate system we use,
> but I think it is right handed (gyro counter clockwise relative to
> acceleration axes).
How do you export the gyro information through the input device?
FWIW, we needed to do extra work in iio-sensor-proxy so that the
accelerometer in the Sixaxis/DS4 joypads (and uDraw tablet) didn't
appear as though they were accelerometer for the system:
https://github.com/hadess/iio-sensor-proxy/commit/401d59e54b3123860180d4401e09df8a1e1bc6c3
> The two other drivers using INPUT_PROC_ACCELEROMETER are hid-wacom and
> hid-udraw-ps3 Wacom. Both seem to report resolution in 'g' as well.
I wrote hid-udraw-ps3, and it's reporting accelerometer data through
input because the rest of the driver is input, and it didn't make much
sense to use another subsystem for just that small portion of the
events the device sends out.
next prev parent reply other threads:[~2019-05-10 8:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 10:09 [RFC v2] iio: input-bridge: optionally bridge iio acceleometers to create a /dev/input interface H. Nikolaus Schaller
2019-04-07 12:30 ` Jonathan Cameron
[not found] ` <CD44AFA0-6676-4842-9C80-61BB363DD556@goldelico.com>
2019-04-14 11:40 ` Jonathan Cameron
2019-04-14 16:26 ` Roderick Colenbrander
2019-05-10 8:57 ` Bastien Nocera [this message]
2019-05-11 18:47 ` Roderick Colenbrander
[not found] ` <CD6219BE-61FF-4C38-9532-054C60A77F89@goldelico.com>
2019-04-22 14:20 ` Jonathan Cameron
2019-05-09 9:09 ` H. Nikolaus Schaller
2019-05-09 17:02 ` [Letux-kernel] " H. Nikolaus Schaller
2019-05-11 11:05 ` Jonathan Cameron
[not found] ` <CCD87A8D-FF65-4681-964B-22870716D655@goldelico.com>
2019-06-08 10:52 ` Jonathan Cameron
2019-05-11 10:54 ` Jonathan Cameron
2019-05-10 8:57 ` Bastien Nocera
2019-05-10 9:33 ` H. Nikolaus Schaller
2019-05-10 9:35 ` Bastien Nocera
2019-05-10 10:06 ` H. Nikolaus Schaller
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=d9f2ee79b8690939f36377990fb6d6fb08e9f0bc.camel@hadess.net \
--to=hadess@hadess.net \
--cc=dmitry.torokhov@gmail.com \
--cc=eric.piel@tremplin-utc.net \
--cc=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-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=thunderbird2k@gmail.com \
/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).