From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Rob Herring <robh@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH/RFC 0/4] ARM: shmobile: Correct masks for GIC PPI interrupts
Date: Tue, 9 Dec 2014 09:29:06 +0900 [thread overview]
Message-ID: <20141209002905.GD8897@verge.net.au> (raw)
In-Reply-To: <CAMuHMdW0ZhRQKuckNkRv3WWQ-6sUez6VP9U3D-W6kpbaqkZaOQ@mail.gmail.com>
On Mon, Dec 08, 2014 at 09:04:16AM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Mon, Dec 8, 2014 at 1:13 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Thu, Nov 27, 2014 at 11:57:15AM +0100, Geert Uytterhoeven wrote:
> >> This patch series corrects the masks in the second interrupt cells for
> >> Private Peripheral Interrupts in dtsi files for the shmobile family of
> >> SoCs.
> >>
> >> It's my understanding this mask should reflect the actual number of CPU
> >> cores the interrupt is wired too.
> >> Is that correct?
> >>
> >> - Hence it should be "GIC_CPU_MASK_SIMPLE(2)" on dual-core CPUs, like
> >> r8a7791 and r8a7794 (the first two patches),
> >> - Should it be "GIC_CPU_MASK_SIMPLE(8)" on big.LITTLE configurations
> >> with four Cortex-A15 cores and four Cortex-A7 cores?
> >> Or should the interrupts be delivered to the four Cortex-A15 cores
> >> only by default?
> >> The last two RFC-patches implement the former for r8a7790 and
> >> r8a73a4.
> >>
> >> Note that incorrect masks for GIC PPI interrupts are not limited to
> >> shmobile. Presumably the interrupt specifiers got copied around a lot,
> >> cfr. the proliferation of "GIC_CPU_MASK_SIMPLE(4)" (and the older
> >> hardcoded "0xf0x" variant) in various dtsi files, not always limited to
> >> quad-core CPUs.
> >>
> >> This was tested on r8a7791/koelsch, which uses the arch timer interrupt.
> >>
> >> Thanks for your feedback!
> >>
> >> Geert Uytterhoeven (4):
> >> ARM: shmobile: r8a7791: Correct mask for GIC PPI interrupts
> >> ARM: shmobile: r8a7794: Correct mask for GIC PPI interrupts
> >
> > Hi Geert,
> >
> > the above two patches seem like they could be queued up.
> > Shall I do so?
>
> I think it's safe. Thanks!
Thanks, I have done so.
prev parent reply other threads:[~2014-12-09 0:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 10:57 [PATCH/RFC 0/4] ARM: shmobile: Correct masks for GIC PPI interrupts Geert Uytterhoeven
2014-11-27 10:57 ` [PATCH 1/4] ARM: shmobile: r8a7791: Correct mask " Geert Uytterhoeven
2014-11-27 10:57 ` [PATCH 2/4] ARM: shmobile: r8a7794: " Geert Uytterhoeven
2014-11-27 10:57 ` [PATCH/RFC 3/4] ARM: shmobile: r8a7790: " Geert Uytterhoeven
2014-11-27 10:57 ` [PATCH/RFC 4/4] ARM: shmobile: r8a73a4: " Geert Uytterhoeven
2014-12-08 0:13 ` [PATCH/RFC 0/4] ARM: shmobile: Correct masks " Simon Horman
2014-12-08 8:04 ` Geert Uytterhoeven
2014-12-09 0:29 ` Simon Horman [this message]
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=20141209002905.GD8897@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marc.zyngier@arm.com \
--cc=robh@kernel.org \
/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).