From: Matthew Hiles <matthew.hiles@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: lenovo yoga 11e touchscreen (baytrail SoC) does not work on 4.0.0 rc2
Date: Tue, 10 Mar 2015 12:52:44 -0400 [thread overview]
Message-ID: <54FF215C.1080002@gmail.com> (raw)
In-Reply-To: <20150310142353.GP1563@lahna.fi.intel.com>
On 03/10/2015 10:23 AM, Mika Westerberg wrote:
> On Wed, Mar 04, 2015 at 05:35:22PM -0500, Matthew Hiles wrote:
>> [ 3.763182] i2c_hid i2c-ITE8386:00: Could not register for ITE8386:00 interrupt, irq = -1, ret = -22
>> [ 3.773742] i2c_hid: probe of i2c-ITE8386:00 failed with error -22
>> [ 3.788298] i2c_hid i2c-ATML1000:00: Could not register for ATML1000:00 interrupt, irq = -1, ret = -22
>> [ 3.806867] i2c_hid: probe of i2c-ATML1000:00 failed with error -22
> This says to me that the device uses GPIOs as interrupts as opposed to
> IOAPIC.
>
> Can you try the following commit?
>
> https://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-4.1/i2c-hid&id=a485923efbb83056b7fb79e4fd2fee05c990ad5e
Progress! Applied that patch to 4.0 rc3 and recompiled:
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
xinput
⎡ Virtual core pointer id=2 [master pointer
(3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎜ ↳ ATML1000:00 03EB:8C1F id=14 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard
(2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard
(3)]
↳ Power Button id=6 [slave keyboard
(3)]
↳ Video Bus id=7 [slave keyboard
(3)]
↳ Power Button id=8 [slave keyboard
(3)]
↳ Sleep Button id=9 [slave keyboard
(3)]
↳ Integrated Camera id=10 [slave keyboard
(3)]
↳ AT Translated Set 2 keyboard id=11 [slave keyboard
(3)]
↳ ThinkPad Extra Buttons id=12 [slave keyboard
(3)]
However, touching the screen does not cause the pointer to move and more
empirically:
(From /proc/bus/input/devices)
I: Bus=0018 Vendor=03eb Product=8c1f Version=0100
N: Name="ATML1000:00 03EB:8C1F"
P: Phys=
S:
Sysfs=/devices/platform/80860F41:01/i2c-9/i2c-ATML1000:00/0018:03EB:8C1F.0001/input/input15
U: Uniq=
H: Handlers=event14 mouse1
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0
B: ABS=260800000000003
Doing
cat /dev/input/event14
or
cat /dev/input/mouse1
and poking the screen gets me no output.
~Matthew
next prev parent reply other threads:[~2015-03-10 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 22:35 PROBLEM: lenovo yoga 11e touchscreen (baytrail SoC) does not work on 4.0.0 rc2 Matthew Hiles
2015-03-10 14:23 ` Mika Westerberg
2015-03-10 16:52 ` Matthew Hiles [this message]
2015-03-11 8:16 ` Mika Westerberg
2015-03-11 12:23 ` Matthew Hiles
2015-03-11 12:42 ` Mika Westerberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54FF215C.1080002@gmail.com \
--to=matthew.hiles@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.