From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Gwendal Grignou <gwendal@chromium.org>,
Bastien Nocera <hadess@hadess.net>
Cc: Hans de Goede <hdegoede@redhat.com>,
Jonathan Cameron <jic23@kernel.org>,
jikos@kernel.org, wpsmith@google.com, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio/hid: Add mount_matrix
Date: Mon, 27 Jun 2022 13:48:35 -0700 [thread overview]
Message-ID: <6f7db3330838b08f5d83c9493a5ccfe25fbab468.camel@linux.intel.com> (raw)
In-Reply-To: <CAPUE2usZS2ww6r67kppn-4WGR7h++c6ioRu-A-ag=h7DpaVSYA@mail.gmail.com>
On Mon, 2022-06-27 at 13:23 -0700, Gwendal Grignou wrote:
> On Mon, Jun 27, 2022 at 2:55 AM Bastien Nocera <hadess@hadess.net>
> wrote:
> >
>
[...]
> Relying on a quirk file for all standalone sensors is not sustainable
> IMHO. I agree changing existing output in newer kernels is also very
> difficult.
> Should we add a new iio sysfs attribute to indicate the sensors
> report
> data according to either the W3C specification or HID specification?
> If present, and set to W3C, iio-sensor-proxy would invert the axis
> first before applying [new] rotation matrices which will never change
> the basis.
When we added support for HID sensor hub, it was primarily driven for
supporting Linux on systems sold with Windows. This started from USB
external hubs to i2c external hubs to now ISH. Still they all are
designed for Windows primarily as OEMs will test on Windows and will
have to pass Windows compliance tests.
We can export the following fields to user space to do any model
specific quirks:
From HID spec:
Property: Sensor Manufacturer
Property: Sensor Model
Property: Sensor Serial Number
Property: Sensor Description
Property: Sensor Connection Type
Connection Type: PC Integrated
Connection Type: PC Attached
Connection Type: PC External
Property: Sensor Device Path
Property: Hardware Revision
Property: Firmware Version
Property: Release Date
Thanks,
Srinivas
next prev parent reply other threads:[~2022-06-27 20:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 22:33 [PATCH] iio/hid: Add mount_matrix Gwendal Grignou
2022-06-25 11:09 ` Jonathan Cameron
2022-06-25 12:33 ` Hans de Goede
2022-06-25 12:40 ` Hans de Goede
2022-06-25 12:52 ` Hans de Goede
2022-06-25 18:26 ` srinivas pandruvada
2022-06-25 20:52 ` Gwendal Grignou
2022-06-26 14:42 ` Hans de Goede
2022-06-27 9:05 ` Gwendal Grignou
2022-06-27 9:55 ` Bastien Nocera
2022-06-27 20:23 ` Gwendal Grignou
2022-06-27 20:48 ` srinivas pandruvada [this message]
2022-06-28 12:44 ` Hans de Goede
2022-06-28 12:33 ` Hans de Goede
2022-07-13 15:58 ` Jonathan Cameron
2022-07-18 10:14 ` Linus Walleij
2022-07-19 1:57 ` Jakob Hauser
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=6f7db3330838b08f5d83c9493a5ccfe25fbab468.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=gwendal@chromium.org \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=wpsmith@google.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