From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934662AbbLRBLH (ORCPT ); Thu, 17 Dec 2015 20:11:07 -0500 Received: from mga04.intel.com ([192.55.52.120]:18835 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934565AbbLRBLE (ORCPT ); Thu, 17 Dec 2015 20:11:04 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,443,1444719600"; d="scan'208";a="876103822" From: "Pandruvada, Srinivas" To: "nish.aravamudan@gmail.com" CC: "lars@metafoo.de" , "linux-kernel@vger.kernel.org" , "knaack.h@gmx.de" , "jic23@kernel.org" , "cmo@melexis.com" , "linux-iio@vger.kernel.org" , "pmeerw@pmeerw.net" , "linux-input@vger.kernel.org" , "jikos@kernel.org" , "Shevchenko, Andriy" Subject: Re: iio/hid-sensor-accel-3d: no output from /dev/iio:device*? Thread-Topic: iio/hid-sensor-accel-3d: no output from /dev/iio:device*? Thread-Index: AQHROS94+E6iDu/JuE++w14keB1+BJ7QdQAAgAAAJ4A= Date: Fri, 18 Dec 2015 01:11:01 +0000 Message-ID: <1450400953.5427.18.camel@intel.com> References: <1450399868.5427.11.camel@linux.intel.com> <1450400312.5427.15.camel@intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.184.10] Content-Type: text/plain; charset="utf-8" Content-ID: <46B7FF2F76319A4FA31FFC06F13E06AF@intel.com> MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id tBI1BC79020503 On Thu, 2015-12-17 at 17:08 -0800, Nish Aravamudan wrote: > On Thu, Dec 17, 2015 at 5:00 PM, Pandruvada, Srinivas > wrote: > > Hi Andy, > > > > As per Nish these patches are impacting sensors on Yoga. > > https://lkml.org/lkml/2015/11/30/441 > > To be clear, without that series, the touchpad and touchscreen on the > Yoga 900 don't work at all. So they are necessary for functioning. I > don't know (I will test it now), if removing the series makes the IIO > sensors work properly in /dev/. This is important to know before we take Andy's time. Thanks, Srinivas > > -Nish > > > On Thu, 2015-12-17 at 16:51 -0800, Srinivas Pandruvada wrote: > > > On Thu, 2015-12-17 at 15:38 -0800, Nish Aravamudan wrote: > > > > [Starting a new thread from > > > > https://lkml.org/lkml/2015/12/15/663, > > > > as > > > > now my laptop is displaying values in the sysfs *raw* files.] > > > > > > > > So I'm trying to understand exactly how the hid-sensor-accel-3d > > > > driver works. > > > > > > > > If I turn up debugging, when I `cat > > > > /sys/bus/iio/devices/device*/*raw*`, I see "iio iio:device3: > > > > accel_3d_proc_event" and I think that means that > > > > hid_sensor_push_data() is getting called. > > > > > > > > But read()'s on /dev/iio:device3 never produces anything, which > > > > is > > > > what iio-sensor-proxy uses to translate events to dbus. > > > > > > > > Is it expected that the dev-node is "silent"? Just trying to > > > > understand if an extension to the driver to support a chardev > > > > based > > > > output is appropriate, or if iio-sensor-proxy needs to be > > > > changed > > > > to > > > > handle this device. > > > > > > You are saying there is some regression. This used to work and > > > now it > > > doesn't work. Is raw values are displayed correctly, when you do > > > "cat"? > > > If cat of raw values is working then power on of sensors is > > > working. > > > > > > Turn on HID debug prints. If it is regression we can do git > > > bisect. > > > Any ACPI or PM changes can break this. Usually there will be > > > GPIOs > > > which will be involved in power on, where ACPI comes into play. > > > This > > > will be done by i2c-hid. There are some prints in i2c-hid which > > > can > > > be > > > enabled also. > > > > > > Thanks, > > > Srinivas > > > > > > > {.n++%ݶw{.n+{G{ayʇڙ,jfhz_(階ݢj"mG?&~iOzv^m ?I