From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Adam Williamson <awilliam@redhat.com>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
"Jin, Yao" <yao.jin@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
alan@linux.intel.com, mathias.nyman@intel.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pinctrl-baytrail: fix for irq descriptor conflict on ASUS T100TA
Date: Wed, 23 Apr 2014 15:23:44 +0300 [thread overview]
Message-ID: <20140423122344.GX30677@intel.com> (raw)
In-Reply-To: <20140423083430.GV30677@intel.com>
On Wed, Apr 23, 2014 at 11:34:30AM +0300, Mika Westerberg wrote:
> On Tue, Apr 22, 2014 at 10:16:50PM -0700, Adam Williamson wrote:
> > Well, I can't actually concur. See my results in
> > https://bugzilla.kernel.org/show_bug.cgi?id=68291#c44 .
> >
> > 1. A kernel with neither patch applied (and no hid-rmi driver) results
> > in a working touchscreen.
> > 2. A kernel with only v3 of Doug's patch from
> > https://bugzilla.kernel.org/show_bug.cgi?id=67921 results in a working
> > touchscreen.
> > 3. A kernel with both v3 of Doug's patch and this IRQ descriptor
> > conflict "fix" results in a broken touchscreen.
> >
> > Seems to me there really is some kind of problem with this patch...
>
> Can you try so that you have both patches applied and then this one? I'm
> suspecting that the ACPI GPIO operation region support might do something
> unexpected in this case.
I'm able to reproduce this problem here now and it seems not related to the
ACPI GPIO operation regions.
This patch changes call to irq_domain_add_linear() to
irq_domain_add_simple() and somehow that changes the behaviour so that I
get non-working touchscreen:
...
[ 37.434998] i2c_hid i2c-ATML1000:00: failed to reset device.
[ 37.435009] i2c_hid i2c-ATML1000:00: i2c_hid_set_power
[ 37.435021] i2c_hid i2c-ATML1000:00: __i2c_hid_command: cmd=fb 00 01 08
[ 38.439897] i2c_hid i2c-ATML1000:00: can't add hid device: -61
[ 38.440749] i2c_hid: probe of i2c-ATML1000:00 failed with error -61
It never gets an interrupt when the device reset is ready.
Jin, do you have any idea what is going on?
next prev parent reply other threads:[~2014-04-23 12:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 12:05 [PATCH] pinctrl-baytrail: fix for irq descriptor conflict on ASUS T100TA Jin Yao
2014-04-18 20:44 ` Benjamin Tissoires
2014-04-18 21:17 ` Adam Williamson
2014-04-20 10:31 ` Jin, Yao
2014-04-20 12:08 ` Jin, Yao
2014-04-20 15:28 ` Adam Williamson
2014-04-21 6:27 ` Jin, Yao
2014-04-21 13:28 ` Jin, Yao
2014-04-21 14:30 ` Benjamin Tissoires
2014-04-21 15:51 ` Adam Williamson
2014-04-23 5:16 ` Adam Williamson
2014-04-23 8:34 ` Mika Westerberg
2014-04-23 12:23 ` Mika Westerberg [this message]
2014-04-23 23:18 ` Adam Williamson
2014-04-24 13:30 ` Jin, Yao
2014-04-24 15:58 ` Adam Williamson
2014-04-24 21:33 ` Adam Williamson
2014-04-25 7:27 ` Jin, Yao
2014-04-25 9:40 ` Mika Westerberg
2014-04-25 12:46 ` Jin, Yao
2014-04-25 9:32 ` Linus Walleij
2014-04-25 15:13 ` Adam Williamson
2014-04-26 3:04 ` Jin, Yao
2014-04-26 3:42 ` Jin, Yao
2014-05-02 22:46 ` Linus Walleij
2014-04-20 12:56 ` Benjamin Tissoires
2014-04-22 11:51 ` Mika Westerberg
2014-04-22 12:46 ` Jin, Yao
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=20140423122344.GX30677@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=awilliam@redhat.com \
--cc=benjamin.tissoires@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=yao.jin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox