From: Bastien Nocera <hadess@hadess.net>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Grant Likely <grant.likely@secretlab.ca>
Cc: Jiri Kosina <jikos@kernel.org>,
benjamin.tissoires@redhat.com,
Jonathan Cameron <jic23@kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
linux-iio@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
chaya.golan@intel.com, daniel.drubin@intel.com,
Darren Hart <darren@dvhart.com>
Subject: Re: [RFC 0/4] Intel Integrated Sensor Hub Support (ISH)
Date: Fri, 10 Jun 2016 16:26:31 +0200 [thread overview]
Message-ID: <1465568791.7409.38.camel@hadess.net> (raw)
In-Reply-To: <1465566904.10525.11.camel@linux.intel.com>
On Fri, 2016-06-10 at 06:55 -0700, Srinivas Pandruvada wrote:
> On Fri, 2016-06-10 at 10:44 +0100, Grant Likely wrote:
> [...]
> >
> > Yes, I do see the in_*_raw_* files in sysfs, and I'm able to get
> > data
> > out of them. Gnome also seems to recognize that the accelerometers
> > are
> > there because it adds a rotation lock button to the system menu.
> >
> > However, the events are getting through yet. It may be that I'm
> > missing something in my kernel config. I'm rebuilding the kernel
> > with
> > Debian's config for the 4.5.5 kernel as a quick sanity test. I'll
> > report back when I've tried.
> >
> You need to add in /usr/lib/system/systemd/iio-sensor-*
>
> After=multi-user.target
>
>
> This service starts too early.
Nobody has been able to explain to me why that would be a problem.
Can you back this up with some data? Does iio-sensor-proxy exit too
early? Does that leave time to the IIO sub-system to do some init work
it should already have done?
See also https://github.com/hadess/iio-sensor-proxy/issues/82
> > I'll also take some time and review the patch series later this
> > afternoon.
>
> Atri Bhattacharya reported issues with suspend/resume. With my test
> patches it is fixed for him
>
> If you want to hold on, I will repost with fixes for susend/resume.
next prev parent reply other threads:[~2016-06-10 14:26 UTC|newest]
Thread overview: 22+ 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-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 [this message]
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
2016-06-02 14:35 me
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=1465568791.7409.38.camel@hadess.net \
--to=hadess@hadess.net \
--cc=benjamin.tissoires@redhat.com \
--cc=chaya.golan@intel.com \
--cc=daniel.drubin@intel.com \
--cc=darren@dvhart.com \
--cc=grant.likely@secretlab.ca \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).