From: Marc Zyngier <marc.zyngier@arm.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Jon Hunter <jonathanh@nvidia.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 16:17:30 +0100 [thread overview]
Message-ID: <57AB458A.4060505@arm.com> (raw)
In-Reply-To: <CACRpkdYixA_E6tePA4hFZrDBAP10No_HkdBvRF3LQNZfxgFpuw@mail.gmail.com>
On 10/08/16 14:50, Linus Walleij wrote:
> On Wed, Aug 10, 2016 at 11:41 AM, Marc Zyngier <marc.zyngier@arm.com> wrote:
>
>> Is this platform related to the Dragonboard 410C? I've got one from
>> Sudeep, and it seems to work fine (though I've spotted a couple of
>> gotchas in the DT).
>
> Nopes this is the ARMv7 APQ8060, the original (first!) dragonboard.
> https://dflund.se/~triad/krad/dragonboard/
>
> (You know me, I always use the odd hardware nobody else use...)
Guess what, I just found this exact sucker in the pile of
"junk we won't ever use because it can't run mainline".
I even booted one of your test images on it.
Do you have a tree I can clone directly, with all the ugly patches
applied?
>
>> Do you see this symptom on all chained interrupts? Or just this
>> particular one?
>
> This appears on all IRQs on the PM (MFD) ASIC.
These interrupts?
197: 1 0 pm8xxx 50 Edge pmic8xxx_pwrkey_release
198: 1 0 pm8xxx 51 Edge pmic8xxx_pwrkey_press
199: 8 0 pm8xxx 74 Edge pmic-keypad
200: 0 0 pm8xxx 75 Edge pmic-keypad-stuck
201: 0 0 pm8xxx 39 Edge pm8xxx_rtc_alarm
How is the interrupt topology built? pm8085 -> tlmm -> GIC?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-08-10 19:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 4:39 [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons 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
2016-08-10 22:06 ` Linus Walleij
2016-08-10 13:50 ` Linus Walleij
2016-08-10 15:17 ` Marc Zyngier [this message]
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=57AB458A.4060505@arm.com \
--to=marc.zyngier@arm.com \
--cc=bjorn.andersson@linaro.org \
--cc=john.stultz@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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