From mboxrd@z Thu Jan 1 00:00:00 1970 From: Srinivas Pandruvada Subject: Re: [PATCH] HID: sensor-hub: Add quirk for Lenovo Yoga 900 with ITE Chips Date: Sat, 19 Dec 2015 09:29:02 -0800 Message-ID: <1450546142.4225.15.camel@linux.intel.com> References: <1450463680-10400-1-git-send-email-srinivas.pandruvada@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from mga02.intel.com ([134.134.136.20]:41804 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933337AbbLSRay (ORCPT ); Sat, 19 Dec 2015 12:30:54 -0500 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Nish Aravamudan Cc: Jiri Kosina , Jonathan Cameron , linux-input@vger.kernel.org On Sat, 2015-12-19 at 09:21 -0800, Nish Aravamudan wrote: > On Fri, Dec 18, 2015 at 10:31 PM, Nish Aravamudan > wrote: > > On Fri, Dec 18, 2015 at 10:34 AM, Srinivas Pandruvada > > wrote: > > > This needs same quirk as applied to other YOGA sensor hubs. > > > Refer to > > > 47eeca8a48 (" HID: sensor-hub: Add in quirk for Lenovo Yogas with > > > ITE") > > > > > > Signed-off-by: Srinivas Pandruvada < > > > srinivas.pandruvada@linux.intel.com> > > > Tested-by: Nishanth Aravamudan > > > > Ok, maybe I spoke too soon! It did work once, at least. But since > > then > > it seems to have stopped working again? That is, the *raw* files > > are > > still working, but iio-sensor-proxy is again not seeing any updates > > via the chardev(s). Any notion of what might be going on? > > > > Note that dmesg does contain (it always has): > > > > i2c_hid i2c-ITE8396:00: error in i2c_hid_init_report size:19 / > > ret_size:18 > > > > but I have no idea if that's relevant to the IIO sensors? I was > > told > > in another thread that it shouldn't have any negative consequence. > > Very strrange! After resuming from suspend this morning to check my > e-mail, it worked again! So maybe there is some bug/race still in the > init/suspend/resume path? As suggested in my previous post, If you want, you can debug i2c hid messages to root causes. > > -Nish