On Sat, 2015-12-19 at 09:21 -0800, Nish Aravamudan wrote:
> On Fri, Dec 18, 2015 at 10:31 PM, Nish Aravamudan
> <nish.aravamudan@xxxxxxxxx> wrote:
> > On Fri, Dec 18, 2015 at 10:34 AM, Srinivas Pandruvada
> > <srinivas.pandruvada@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx>
> > > Tested-by: Nishanth Aravamudan <nish.aravamudan@xxxxxxxxx>
> >
> > 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
--
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
