From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932404AbcFJPEr (ORCPT ); Fri, 10 Jun 2016 11:04:47 -0400 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:41875 "EHLO relay4-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751951AbcFJPEq (ORCPT ); Fri, 10 Jun 2016 11:04:46 -0400 X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 09 hex): References: ...druvada@linux.intel.com>\n\t\n\t Subject: Re: [RFC 0/4] Intel Integrated Sensor Hub Support (ISH) From: Bastien Nocera To: Srinivas Pandruvada , Grant Likely Cc: Jiri Kosina , benjamin.tissoires@redhat.com, Jonathan Cameron , "linux-input@vger.kernel.org" , linux-iio@vger.kernel.org, Linux Kernel Mailing List , chaya.golan@intel.com, daniel.drubin@intel.com, Darren Hart Date: Fri, 10 Jun 2016 17:04:36 +0200 In-Reply-To: <1465569941.10525.17.camel@linux.intel.com> References: <1464668878-17113-1-git-send-email-srinivas.pandruvada@linux.intel.com> <1465509287.24319.3.camel@linux.intel.com> <1465566904.10525.11.camel@linux.intel.com> <1465568791.7409.38.camel@hadess.net> <1465569941.10525.17.camel@linux.intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.2 (3.20.2-1.fc24) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2016-06-10 at 07:45 -0700, Srinivas Pandruvada wrote: > On Fri, 2016-06-10 at 16:26 +0200, Bastien Nocera wrote: > > 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? > The driver's  trigger callback doesn't even get called to take any > action or provide any data. So to get called need to restart the > service or do suspend/resume. Are there any errors when setting the triggers? The code there is probably a bit naive, but I'd rather fix that rather than postpone the start of the daemon. > After=multi-user.target, is not the ideal solution as it is too late. > So need further debug. > > > > > 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. > > > -- > To unsubscribe from this list: send the line "unsubscribe linux- > input" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at  http://vger.kernel.org/majordomo-info.html