linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"Song, Hongyan" <hongyan.song@intel.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"hadess@hadess.net" <hadess@hadess.net>
Cc: "jikos@kernel.org" <jikos@kernel.org>,
	"jic23@kernel.org" <jic23@kernel.org>
Subject: Re: [PATCH] iio: hid: hid-sensor-accel-3d: Add second ACC sensor support
Date: Fri, 17 Mar 2017 16:22:09 +0000	[thread overview]
Message-ID: <1489767728.88966.8.camel@intel.com> (raw)
In-Reply-To: <1489756594.18490.22.camel@hadess.net>

On Fri, 2017-03-17 at 14:16 +0100, Bastien Nocera wrote:
> On Fri, 2017-03-17 at 02:13 +0000, Pandruvada, Srinivas wrote:
> > 
> > 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.
> > 
> > This type of interface will not satisfy all cases. We have some
> > hubs
> > with  many accelerometers attached. Same case is also true even for
> > discrete sensors. So there should be some framework way to expose
> > location of sensors.
> 
> So you're nacking as well?
Yes.

> 
> > 
> > ACPI has special method called _PLD (Physical Device Location),
> > which
> > can  be used to specify location of any device. So we need to be
> > able
> > to export such information to user space. We can add for each
> > sensor
> > the location information.
> > 
> > I can propose some ABI for exporting location information.
> 
> There were patches floating around to do this, but they were never
> finished:
> http://www.spinics.net/lists/linux-acpi/msg51540.html
We need to add some of those element related to sensors to IIO ABI.
I will propose an ABI as Jonathan suggested.

Thanks,
Srinivas

      parent reply	other threads:[~2017-03-17 16:23 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
     [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 [this message]

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=1489767728.88966.8.camel@intel.com \
    --to=srinivas.pandruvada@intel.com \
    --cc=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 \
    /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).