From: Bastien Nocera <hadess@hadess.net>
To: Song Hongyan <hongyan.song@intel.com>,
linux-input@vger.kernel.org, linux-iio@vger.kernel.org
Cc: jikos@kernel.org, jic23@kernel.org, srinivas.pandruvada@intel.com
Subject: Re: [PATCH] iio: hid: hid-sensor-accel-3d: Add second ACC sensor support
Date: Thu, 16 Mar 2017 13:01:42 +0100 [thread overview]
Message-ID: <1489665702.18490.12.camel@hadess.net> (raw)
In-Reply-To: <1489659652-35608-1-git-send-email-hongyan.song@intel.com>
On Thu, 2017-03-16 at 18:20 +0800, Song Hongyan wrote:
> As accelerometer sensor becomes more and more popular, there are more
> user scenarios have been developed, "Hinge" is a very important
> usecase
> which needs two accelerometer sensors to calculate the included angle
> of keyboard and screen.
> In this case, two accelerometer sensors will be exposed. Currently,
> IIO interface hasn't other way to distinguish two sensors with same
> sensor type, except sensor name. So a new sensor name "accel_2nd_3d"
> is added for secondary accelerometer sensor.
>
> In HID level, connection type is a good common property to
> differentiate two sensors with same sensor type.
I've been told in the past not to rely on device names in iio-sensor-
proxy, and this would go against this advice.
As you have a "type" to export, why not export that instead?
next prev parent reply other threads:[~2017-03-16 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 10:20 [PATCH] iio: hid: hid-sensor-accel-3d: Add second ACC sensor support Song Hongyan
2017-03-16 12:01 ` Bastien Nocera [this message]
[not found] ` <1489665702.18490.12.camel-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
2017-03-17 1:21 ` Song, Hongyan
2017-03-17 13:14 ` Bastien Nocera
[not found] ` <1489659652-35608-1-git-send-email-hongyan.song-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-03-17 2:13 ` Pandruvada, Srinivas
2017-03-17 13:16 ` Bastien Nocera
[not found] ` <1489756594.18490.22.camel-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
2017-03-17 13:31 ` Jonathan Cameron
2017-03-17 16:22 ` Pandruvada, Srinivas
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=1489665702.18490.12.camel@hadess.net \
--to=hadess@hadess.net \
--cc=hongyan.song@intel.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=srinivas.pandruvada@intel.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).