From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms@verge.net.au>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
linux-renesas-soc@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/2] ARM: dts: shmobile: Correct interrupt type for ARM TWD
Date: Tue, 22 Mar 2016 09:43:40 +0100 [thread overview]
Message-ID: <CAMuHMdXcew-NHGeb2x69CR4ZBeyf3hET3xtQYSkToSX9BD68uw@mail.gmail.com> (raw)
In-Reply-To: <20160322012849.GA14367@verge.net.au>
Hi Simon,
On Tue, Mar 22, 2016 at 2:28 AM, Simon Horman <horms@verge.net.au> wrote:
> On Fri, Mar 18, 2016 at 11:19:19AM +0100, Geert Uytterhoeven wrote:
>> This patch series corrects the interrupt type for ARM TWD timers on
>> SH-Mobile AG5 and R-Car H1.
>>
>> The ARM TWD interrupt is a private peripheral interrupt (PPI), and per
>> the ARM GIC documentation, whether the type for PPIs can be set is
>> IMPLEMENTATION DEFINED.
>>
>> For SH-Mobile AG5 and R-Car H1 devices the PPI type cannot be set, and
>> so when we attempt to set the type for the ARM TWD interrupt it fails.
>> This has gone unnoticed because it fails silently, and because we cannot
>> re-configure the type it has had no impact. Nevertheless fix the type
>> for the TWD interrupt so that it matches the hardware configuration.
>>
>> This was exposed by Jon Hunter's "[PATCH 04/15] irqchip/gic: WARN if
>> setting the interrupt type fails" (https://lkml.org/lkml/2016/3/17/339),
>> which triggers:
>>
>> WARNING: CPU: 0 PID: 0 at drivers/irqchip/irq-gic-common.c:61 gic_configure_irq+0x64/0x7c()
>>
>> Other Renesas SoCs using private peripheral interrupts (R-Mobile APE6,
>> R-Car Gen2, and R-Car Gen3) seem to be fine.
>>
>> Based on patches by Jon Hunter for Tegra20/30 and OMAP4.
>
> Thanks for this. Do you think it would be best to queue these up
> for v4.7 or as fixes for v4.6?
I don't know if/when Jon's patch will go in, but he's tracking the fixes for
various SoCs, as we don't know yet how many are affected.
So I think it's basically up to you.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2016-03-22 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 10:19 [PATCH 0/2] ARM: dts: shmobile: Correct interrupt type for ARM TWD Geert Uytterhoeven
2016-03-18 10:19 ` [PATCH 1/2] ARM: dts: sh73a0: " Geert Uytterhoeven
2016-03-18 10:19 ` [PATCH 2/2] ARM: dts: r8a7779: " Geert Uytterhoeven
2016-03-22 1:28 ` [PATCH 0/2] ARM: dts: shmobile: " Simon Horman
2016-03-22 8:43 ` Geert Uytterhoeven [this message]
2016-03-23 0:48 ` Simon Horman
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=CAMuHMdXcew-NHGeb2x69CR4ZBeyf3hET3xtQYSkToSX9BD68uw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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;
as well as URLs for NNTP newsgroup(s).