Re: PROBLEM: lenovo yoga 11e touchscreen (baytrail SoC) does not work on 4.0.0 rc2

From: Mika Westerberg
Date: Wed Mar 11 2015 - 08:43:06 EST


On Wed, Mar 11, 2015 at 08:23:54AM -0400, Matthew Hiles wrote:
>
>
> On 03/11/2015 04:16 AM, Mika Westerberg wrote:
> >On Tue, Mar 10, 2015 at 12:52:44PM -0400, Matthew Hiles wrote:
> >>uname -a
> >>Linux pontifex 4.0.0-1-ARCH #2 SMP PREEMPT Tue Mar 10 11:54:37 EDT 2015
> >>x86_64 GNU/Linux
> >>
> >>dmesg|grep hid
> >>[ 3.850715] hidraw: raw HID events driver (C) Jiri Kosina
> >>[ 8.873837] i2c_hid i2c-ITE8386:00: failed to reset device.
> >>[ 14.895347] i2c_hid i2c-ITE8386:00: failed to reset device.
> >>[ 20.916806] i2c_hid i2c-ITE8386:00: failed to reset device.
> >>[ 26.938430] i2c_hid i2c-ITE8386:00: failed to reset device.
> >>[ 27.956009] i2c_hid i2c-ITE8386:00: can't add hid device: -61
> >>[ 27.976242] i2c_hid: probe of i2c-ITE8386:00 failed with error -61
> >>[ 28.028155] hid-multitouch 0018:03EB:8C1F.0001: input,hidraw0: <UNKNOWN>
> >>HID v1.00 Device [ATML1000:00 03EB:8C1F] on
> >Can you send me acpidump from your machine?
>
>
> Attached.

Thanks.

Unfortunately it did not reveal anything new :-(

I did few more changes to the Baytrail pinctrl driver which are now
included in linux-next. Can you try with the latest linux-next or
alternatively cherry-pick following commits on top of 4.0-rc3:

a485923efbb8 HID: i2c-hid: Add support for ACPI GPIO interrupts
6d00f37e49d9 HID: i2c-hid: Limit reads to wMaxInputLength bytes for input events
f2de746c3f03 HID: i2c-hid: The interrupt should be level sensitive
fcc18deb7682 pinctrl: baytrail: Save pin context over system sleep
31e4329f9906 pinctrl: baytrail: Rework interrupt handling
95f0972c7e4c pinctrl: baytrail: Clear interrupt triggering from pins that are in GPIO mode
f8323b6bb2cc pinctrl: baytrail: Relax GPIO request rules
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/