Hi,
On Thu, 2016-06-02 at 09:48 +0200, Atri Bhattacharya wrote:
> On Thu, 2016-06-02 at 03:27 +0000, Srinivas Pandruvada wrote:
> > 
> > Atri Bhattacharya <badshah400@...> writes:
> > 
> > > 
> > >  
[...]
> > > +
> >  #include <linux/device.h>
> >  #include <linux/hid.h>
> >  #include <linux/module.h>
> > @@ -798,6 +799,9 @@ static const struct hid_device_id
> > sensor_hub_devices[] = 
> > {
> >         { HID_DEVICE(HID_BUS_ANY, HID_GROUP_SENSOR_HUB,
> > USB_VENDOR_ID_ITE,
> >                         USB_DEVICE_ID_ITE_LENOVO_YOGA900),
> >                         .driver_data = HID_SENSOR_HUB_ENUM_QUIRK},
> > +       { HID_DEVICE(HID_BUS_ANY, HID_GROUP_SENSOR_HUB, 
> > USB_VENDOR_ID_INTEL_0,
> > +                       0x22D8),
> > +                       .driver_data = HID_SENSOR_HUB_ENUM_QUIRK},
> >         { HID_DEVICE(HID_BUS_ANY, HID_GROUP_SENSOR_HUB, HID_ANY_ID,
> >                      HID_ANY_ID) },
> >         { }
> > 
> > 
> Thanks for your response, but this patch didn't help with the slow
> suspend/wakeup problem or with making the device actually respond to
> rotation or brightness changes. At this stage the sensor-hub seems to
> be recognised just fine, but not to be working. Same messages as
> above
> continue to show up in the journal.
> 
Looks like the system resume is getting timed out. I am looking at
possible issue on Yoga 260.
Meanwhile can you try:
- Raw reads (cat /sys/bus/iio/devices/iio:device (your device
 index)/in_accel_?_raw
- The attached is a program. Don't start iio_sensor_proxy service.
Disable so that it doesn't start on boot and run
sensor_monitor -n accel_3d

Thanks,
Srinivas






> Best wishes
> -- 
> Atri Bhattacharya
> Thu  2 Jun 09:42:21 CEST 2016
> 
> Sent from openSUSE Tumbleweed (20160530) (x86_64) on my laptop.