From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Sébastien Bourdeauducq" <sb@m-labs.hk>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
linux-input <linux-input@vger.kernel.org>
Subject: Re: "i2c_hid: Could not register for interrupt, irq = -1" on Thinkpad Tablet 10
Date: Tue, 3 Feb 2015 13:25:14 +0200 [thread overview]
Message-ID: <20150203112514.GC18758@lahna.fi.intel.com> (raw)
In-Reply-To: <54D08C7A.6070905@m-labs.hk>
On Tue, Feb 03, 2015 at 04:53:14PM +0800, Sébastien Bourdeauducq wrote:
> On 02/02/2015 11:57 PM, Mika Westerberg wrote:
> >> > Maybe the interrupt should be level sensitive and enabled only after
> >> > certain parts of the device initialization have taken place.
> > The device should respond to reset by asserting an interrupt. You could
> > try so that you only enable the interrupt in i2c_hid_parse() right
> > before i2c_hid_hwreset() is called.
>
> No luck. There is no more interrupt flood and the device is detected and
> its report descriptor retrieved, but then no events at all are received
> when using the stylus.
If you now check the GPIO status in /sys/kernel/debug/gpio, does it show
'high'?
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-02-03 11:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 15:01 "i2c_hid: Could not register for interrupt, irq = -1" on Thinkpad Tablet 10 Sebastien Bourdeauducq
2015-01-31 20:39 ` Benjamin Tissoires
2015-02-01 3:27 ` Sebastien Bourdeauducq
2015-02-02 10:00 ` Mika Westerberg
2015-02-02 13:19 ` Sebastien Bourdeauducq
2015-02-02 13:48 ` Mika Westerberg
2015-02-02 15:32 ` Sébastien Bourdeauducq
2015-02-02 15:42 ` Benjamin Tissoires
2015-02-02 15:55 ` Sébastien Bourdeauducq
2015-02-02 15:57 ` Mika Westerberg
2015-02-03 8:53 ` Sébastien Bourdeauducq
2015-02-03 11:25 ` Mika Westerberg [this message]
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=20150203112514.GC18758@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=benjamin.tissoires@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=sb@m-labs.hk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).