On Tue, 2016-06-14 at 14:44 +0100, Grant Likely wrote: > On Fri, Jun 10, 2016 at 4:27 PM, Bastien Nocera <hadess@xxxxxxxxxx> > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
