From: Atri Bhattacharya <badshah400@aim.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [RFC 0/4] Intel Integrated Sensor Hub Support (ISH)
Date: Fri, 03 Jun 2016 04:50:40 +0200 [thread overview]
Message-ID: <1464922240.3161.2.camel@aim.com> (raw)
In-Reply-To: <1464907711.3970.70.camel@linux.intel.com>
On Thu, 2016-06-02 at 15:48 -0700, Srinivas Pandruvada wrote:
> On Fri, 2016-06-03 at 00:29 +0200, Atri Bhattacharya wrote:
> > Hi Srinivas,
> >
> > On Thu, 2016-06-02 at 21:44 +0000, Pandruvada, Srinivas wrote:
> > >
> > > On Thu, 2016-06-02 at 13:00 -0700, Srinivas Pandruvada wrote:
> > > >
> > > > Hi,
> > > >
> > > > Thanks for your help in evaluation.
> > > >
> > > >
> > > > [...]
> > > >
> > > > The iio sensor proxy starts too soon. So I recommended to wait
> > > > for
> > > > mult-user target before start. I think developer is
> > > > considering.
> > > >
> > > Add after "Description" in the section [Unit] in systemd unit
> > > file
> > > /usr/lib/systemd/system/iio-sensor-proxy.service
> > >
> > > After=multi-user.target
> > >
> > > Your rotation should work on Yoga 260. I tried on Fedora 23.
> > >
> > It does! Thank you so much for this tip. Well, it doesn't work
> > again
> > after suspend/wakeup but I will let you know if that issue gets
> > fixed
> > after the patched kernel finishes building.
> The problem is iio_proxy keeps open the IIO file handles, but ISH FW
> is
> will powerup again after suspend, which causes issue. So may be by
> systemd magic stop the service and start again on resume.
>
> I am working on this. So probably in RFC v2, I will have some fix.
>
One thing I just noticed is that the iio device number change after a
suspend/wakeup cycle. For e.g., immediately after booting the
in_accel_?_raw files are located in the dir
/sys/bus/iio/devices/iio\:device0/
but after a suspend/wakeup the in_accel files have moved to
/sys/bus/iio/devices/iio\:device3/
instead. No idea if this is relevant or not, just thought I should let
you know.
--
Atri Bhattacharya
Fri 3 Jun 04:47:15 CEST 2016
Sent from openSUSE Tumbleweed (20160531) (x86_64) on my laptop.
next prev parent reply other threads:[~2016-06-03 2:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 4:27 [RFC 0/4] Intel Integrated Sensor Hub Support (ISH) Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 1/4] Documentation: hid: Intel ISH HID document Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 2/4] hid: intel_ish-hid: ISH Transport layer Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 3/4] hid: intel-ish-hid: ipc layer Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 4/4] hid: intel-ish-hid: ISH HID client driver Srinivas Pandruvada
2016-06-01 13:36 ` [RFC 0/4] Intel Integrated Sensor Hub Support (ISH) Atri Bhattacharya
2016-06-02 3:27 ` Srinivas Pandruvada
2016-06-02 7:48 ` Atri Bhattacharya
2016-06-02 16:49 ` Srinivas Pandruvada
2016-06-02 19:42 ` Atri Bhattacharya
2016-06-02 20:00 ` Srinivas Pandruvada
2016-06-02 21:44 ` Pandruvada, Srinivas
2016-06-02 22:29 ` Atri Bhattacharya
2016-06-02 22:48 ` Srinivas Pandruvada
2016-06-02 22:57 ` Atri Bhattacharya
2016-06-02 23:13 ` Atri Bhattacharya
2016-06-03 2:50 ` Atri Bhattacharya [this message]
2016-06-03 4:01 ` Srinivas Pandruvada
2016-06-03 3:08 ` Atri Bhattacharya
2016-06-03 4:02 ` Srinivas Pandruvada
2016-06-06 6:47 ` Srinivas Pandruvada
2016-06-09 21:45 ` Grant Likely
2016-06-09 21:54 ` Srinivas Pandruvada
2016-06-10 9:44 ` Grant Likely
2016-06-10 13:55 ` Srinivas Pandruvada
2016-06-10 14:26 ` Bastien Nocera
2016-06-10 14:45 ` Srinivas Pandruvada
2016-06-10 15:04 ` Bastien Nocera
2016-06-10 15:23 ` Srinivas Pandruvada
2016-06-10 15:27 ` Bastien Nocera
2016-06-14 13:44 ` Grant Likely
2016-06-14 15:12 ` Bastien Nocera
2016-06-14 16:08 ` Grant Likely
2016-06-14 17:01 ` Bastien Nocera
2016-06-14 21:33 ` Grant Likely
2016-06-10 14:02 ` Grant Likely
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=1464922240.3161.2.camel@aim.com \
--to=badshah400@aim.com \
--cc=linux-iio@vger.kernel.org \
--cc=srinivas.pandruvada@linux.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).