All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	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: Tue, 14 Jun 2016 17:12:03 +0200	[thread overview]
Message-ID: <1465917123.606.11.camel@hadess.net> (raw)
In-Reply-To: <CACxGe6sjFHS9VaeWUY1PsJXhTW1Nvkuoqutty9oSX2Ywj+yV9g@mail.gmail.com>

On Tue, 2016-06-14 at 14:44 +0100, Grant Likely wrote:
> On Fri, Jun 10, 2016 at 4:27 PM, Bastien Nocera <hadess@hadess.net>
> wrote:
> > On Fri, 2016-06-10 at 08:23 -0700, Srinivas Pandruvada wrote:
> > > On Fri, 2016-06-10 at 17:04 +0200, Bastien Nocera wrote:
> > > > > 
> > > 
> > > [...]
> > > 
> > > > Are there any errors when setting the triggers?
> > > > 
> > > Is there any debug option in this service to give more verbose
> > > output?
> > 
> > Add:
> > Environment="G_MESSAGES_DEBUG=all"
> > 
> > To the service file. You should see the debug in systemctl:
> > systemctl status iio-sensor-proxy.service
> > 
> > Or in journalctl if there's too much data:
> > journalctl --reverse -u iio-sensor-proxy.service
> 
> Still no joy on the sensors. The proxy starts up and detects the
> sensors, but I don't see any sensor events occurring:

Could you try again with the current master of iio-sensor-proxy? Make
sure to install the file in the same location as in your distro
provided package.

I've added more debug/warnings to a few cases where it would have
silently failed in the past.

In particular, I don't see any messages that would be coming out of:
https://github.com/hadess/iio-sensor-proxy/blob/master/src/iio-buffer-utils.c#L512

Could it be that the sub-directory is populated after the device is
created in the kernel, causing a race?

Either that, or the contents of the scan_elements/ directory is not the
one expected by this code.

The output of this command should us that:
ls /sys/devices/pci0000:00/0000:00:13.0/{33AECD58-B679-4E54-9BD9-A04D34F0C226}/001E:8086:22D8.0001/HID-SENSOR-200073.8.auto/iio:device1/scan_elements

Cheers

  reply	other threads:[~2016-06-14 15:12 UTC|newest]

Thread overview: 48+ 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
     [not found] ` <1464668878-17113-1-git-send-email-srinivas.pandruvada-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-05-31  4:27   ` [RFC 1/4] Documentation: hid: Intel ISH HID document Srinivas Pandruvada
2016-05-31  4:27     ` 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-01 13:36   ` Atri Bhattacharya
2016-06-01 13:36   ` 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
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-09 21:54     ` Srinivas Pandruvada
     [not found]     ` <1465509287.24319.3.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-06-10  9:44       ` Grant Likely
2016-06-10  9:44         ` Grant Likely
2016-06-10 13:55         ` Srinivas Pandruvada
2016-06-10 14:26           ` Bastien Nocera
     [not found]             ` <1465568791.7409.38.camel-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
2016-06-10 14:45               ` Srinivas Pandruvada
2016-06-10 14:45                 ` Srinivas Pandruvada
2016-06-10 15:04                 ` Bastien Nocera
2016-06-10 15:04                   ` Bastien Nocera
     [not found]                   ` <1465571076.7409.39.camel-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
2016-06-10 15:23                     ` Srinivas Pandruvada
2016-06-10 15:23                       ` Srinivas Pandruvada
     [not found]                       ` <1465572227.24319.7.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-06-10 15:27                         ` Bastien Nocera
2016-06-10 15:27                           ` Bastien Nocera
     [not found]                           ` <1465572452.7409.41.camel-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
2016-06-14 13:44                             ` Grant Likely
2016-06-14 13:44                               ` Grant Likely
2016-06-14 15:12                               ` Bastien Nocera [this message]
2016-06-14 16:08                                 ` Grant Likely
2016-06-14 17:01                                   ` Bastien Nocera
2016-06-14 21:33                                     ` Grant Likely
     [not found]         ` <CACxGe6vq-FDpjG8WtrraveQo+ZT3MHMDFzrA5-qqNLEwcbmNhw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-10 14:02           ` Grant Likely
2016-06-10 14:02             ` Grant Likely
  -- strict thread matches above, loose matches on Subject: below --
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=1465917123.606.11.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.