From: Jon Hunter <jonathanh@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons
Date: Wed, 10 Aug 2016 15:12:21 +0100 [thread overview]
Message-ID: <a54e783a-3e17-8554-efd2-d84c0ae2c71a@nvidia.com> (raw)
In-Reply-To: <CACRpkdZrAfFmeYwciOegeqTWsi+Lhg31tkGq0JWoRR47KMb9iQ@mail.gmail.com>
On 10/08/16 14:58, Linus Walleij wrote:
> On Wed, Aug 10, 2016 at 11:56 AM, Jon Hunter <jonathanh@nvidia.com> wrote:
>> Hi Marc, Linus,
>> On 10/08/16 10:41, Marc Zyngier wrote:
>>> On 10/08/16 00:03, Linus Walleij wrote:
>>>> On Tue, Aug 9, 2016 at 3:20 PM, Jon Hunter <jonathanh@nvidia.com> wrote:
>>>>
>>>>> If that works, then does the following also work (without the above) ...
>>>>>
>>>>> diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
>>>>> index b4c1bc7c9ca2..e111b72e3162 100644
>>>>> --- a/kernel/irq/chip.c
>>>>> +++ b/kernel/irq/chip.c
>>>>> @@ -824,6 +824,7 @@ __irq_do_set_handler(struct irq_desc *desc, irq_flow_handler_t handle,
>>>>> irq_settings_set_norequest(desc);
>>>>> irq_settings_set_nothread(desc);
>>>>> desc->action = &chained_action;
>>>>> + __irq_set_trigger(desc, irqd_get_trigger_type(&desc->irq_data));
>>>>> irq_startup(desc, true);
>>>>> }
>>>>> }
> (...)
>>>> I tried this on my problematic platform and then this happens:
>>>>
>>>> preparing networking...
>>>> [ 2.628246] ------------[ cut here ]------------
>>>> [ 2.628303] WARNING: CPU: 0 PID: 92 at ../kernel/irq/chip.c:26
>>>> bad_chained_irq+0x44/0x4c
> (...)
>> Just to confirm is that with or without the proposed change?
>
> This is with:
> + __irq_set_trigger(desc, irqd_get_trigger_type(&desc->irq_data));
>
> No other changes.
>
> Before the change it boots, but the IRQs don't work.
>
> After the change it boots and crashes like that.
OK.
>> Linus, I have been trying to find out which qcom board has this smsc911x
>> but I was unable to find any, so more info on the platform would be great!
>
> It has nothing to do with the SMSC911x per se. The problem pertains
> to *all* IRQs from the PMIC.
>
> This is the original APQ8060 Dragonboard from BSquare.
> https://dflund.se/~triad/krad/dragonboard/
Where can I see the DT source for this board? There is a
arch/arm/boot/dts/qcom-apq8060-dragonboard.dts but this does not appear
to be the same (does not have smsc911x).
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2016-08-10 20:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 4:39 John Stultz
2016-07-30 4:52 ` Bjorn Andersson
2016-07-30 11:10 ` Marc Zyngier
2016-07-30 8:07 ` Thomas Gleixner
2016-08-05 18:12 ` John Stultz
2016-08-08 9:04 ` Jon Hunter
2016-08-08 21:50 ` Linus Walleij
2016-08-08 21:35 ` Linus Walleij
2016-08-01 10:26 ` Jon Hunter
2016-08-05 23:45 ` John Stultz
2016-08-08 9:31 ` Jon Hunter
2016-08-09 4:25 ` John Stultz
2016-08-09 13:20 ` Jon Hunter
2016-08-09 15:08 ` Marc Zyngier
2016-08-09 23:03 ` Linus Walleij
2016-08-10 9:41 ` Marc Zyngier
2016-08-10 9:56 ` Jon Hunter
2016-08-10 10:21 ` Marc Zyngier
2016-08-10 13:58 ` Linus Walleij
2016-08-10 14:12 ` Jon Hunter [this message]
2016-08-10 22:06 ` Linus Walleij
2016-08-10 13:50 ` Linus Walleij
2016-08-10 15:17 ` Marc Zyngier
2016-08-10 22:14 ` Linus Walleij
2016-08-08 21:48 ` Linus Walleij
2016-08-11 8:37 ` Marc Zyngier
2016-08-11 9:47 ` Jon Hunter
2016-08-11 11:45 ` Marc Zyngier
2016-08-11 11:53 ` Marc Zyngier
2016-08-11 12:46 ` Marc Zyngier
2016-08-11 13:29 ` Jon Hunter
2016-08-11 13:34 ` Marc Zyngier
2016-08-11 15:32 ` John Stultz
2016-08-11 15:51 ` Marc Zyngier
2016-08-11 21:08 ` Linus Walleij
2016-08-11 21:23 ` Bjorn Andersson
2016-08-12 10:22 ` Marc Zyngier
2016-08-11 12:01 ` Linus Walleij
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=a54e783a-3e17-8554-efd2-d84c0ae2c71a@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=bjorn.andersson@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome