From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Adam Williamson <awilliam@redhat.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Alan Cox <alan@linux.intel.com>,
Mathias Nyman <mathias.nyman@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] pinctrl-baytrail: fix for irq descriptor conflict on ASUS T100TA
Date: Sat, 26 Apr 2014 11:42:45 +0800 [thread overview]
Message-ID: <535B2B35.2090502@linux.intel.com> (raw)
In-Reply-To: <535B2250.2010509@linux.intel.com>
On 2014/4/26 11:04, Jin, Yao wrote:
>
>
> On 2014/4/25 23:13, Adam Williamson wrote:
>> On Fri, 2014-04-25 at 11:32 +0200, Linus Walleij wrote:
>>> On Thu, Apr 24, 2014 at 11:33 PM, Adam Williamson <awilliam@redhat.com> wrote:
>>>
>>>> Well, I just ran another test too. I built a kernel (3.15rc2) with both
>>>> v3 of Doug's SDIO device enumeration patch -
>>>> http://dougvj.net/baytrail_gpio_quirk_v3.patch - and the new patch for
>>>> the IRQ allocation issue by Thomas Gleixner,
>>>> https://patchwork.kernel.org/patch/4051581/ . That kernel gives me a
>>>> working touchscreen. Note that
>>>> http://dougvj.net/baytrail_gpio_quirk_v3.patch includes both the blocks
>>>> you mention (i.e. it adds INT33FC in both places).
>>>>
>>>> So, it really seems like for me at least, it's the combination of Doug's
>>>> patch and your approach to fixing the IRQ allocation issue that breaks
>>>> the touchscreen. Thomas' approach, even combined with Doug's patch,
>>>> seems to work fine.
>>>
>>> Please make sure to provide a Tested-by: tag to Thomas so he
>>> knows this is merge material.
>>
>> Well, I'd rather someone test on the box that's actually affected by the
>> IRQ allocation conflict lockups so we can confirm it actually fixes
>> them :)
>>
>
> I have tried the Thomas Gleixner's patch on 3.14.0 with i915 loading,
> the irq conflict disappears.
> --
I think we still need a small modification on pinctrl-baytrail.c, that
is moving gpiochip_add forward, otherwise the to_irq method is not set.
diff --git a/drivers/pinctrl/pinctrl-baytrail.c
b/drivers/pinctrl/pinctrl-baytrail.c
index e599834..fdfb84b 100644
--- a/drivers/pinctrl/pinctrl-baytrail.c
+++ b/drivers/pinctrl/pinctrl-baytrail.c
@@ -491,12 +491,6 @@ static int byt_gpio_probe(struct platform_device *pdev)
gc->can_sleep = false;
gc->dev = dev;
- ret = gpiochip_add(gc);
- if (ret) {
- dev_err(&pdev->dev, "failed adding byt-gpio chip\n");
- return ret;
- }
-
/* set up interrupts */
irq_rc = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
if (irq_rc && irq_rc->start) {
@@ -514,6 +508,12 @@ static int byt_gpio_probe(struct platform_device *pdev)
irq_set_chained_handler(hwirq, byt_gpio_irq_handler);
}
+ ret = gpiochip_add(gc);
+ if (ret) {
+ dev_err(&pdev->dev, "failed adding byt-gpio chip\n");
+ return ret;
+ }
+
pm_runtime_enable(dev);
return 0;
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2014-04-26 3:42 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
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 [this message]
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=535B2B35.2090502@linux.intel.com \
--to=yao.jin@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=mika.westerberg@linux.intel.com \
--cc=tglx@linutronix.de \
/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.