From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: DTS: Fix broken GICv2 register maps
Date: Wed, 18 Jan 2017 13:34:30 +0100 [thread overview]
Message-ID: <2966702.djJyWhCMlK@wuerfel> (raw)
In-Reply-To: <1484736811-24002-1-git-send-email-marc.zyngier@arm.com>
On Wednesday, January 18, 2017 10:53:29 AM CET Marc Zyngier wrote:
> For a GICv2 (which happens to be virtualization capable), the
> architecture mandates the following regions:
>
> GICD: 4kB
> GICC: 8kB
> GICH: 8kB
> GICV: 8kB
>
> Unfortunately, I made a mistake in one of the examples contained in
> the DT binding document, and everyone duplicated that same mistake all
> over the map.
>
> This small series fixes the DT binding, and hopefully updates all the
> offending DTs to be compliant with the architecture.
>
Looks good to me, can you send this as a pull request to arm at kernel.org
once you have collected a reasonable number of Acks?
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2017-01-18 12:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 10:53 [PATCH 0/2] ARM: DTS: Fix broken GICv2 register maps Marc Zyngier
2017-01-18 10:53 ` [PATCH 1/2] dt-bindings: arm, gic: Fix binding example for a virt-capable GIC Marc Zyngier
2017-01-19 14:40 ` [PATCH 1/2] dt-bindings: arm,gic: " Mark Rutland
2017-01-18 10:53 ` [PATCH 2/2] ARM: DTS: Fix register map for " Marc Zyngier
2017-01-18 11:25 ` Heiko Stübner
2017-01-18 11:29 ` Matthias Brugger
2017-01-18 11:57 ` Robin Murphy
2017-01-18 13:25 ` Marc Zyngier
2017-01-18 12:49 ` Antoine Tenart
2017-01-18 13:23 ` Maxime Ripard
2017-01-18 14:09 ` Krzysztof Kozlowski
2017-01-18 15:16 ` Javier Martinez Canillas
2017-01-18 15:26 ` Marc Zyngier
2017-01-18 16:39 ` Santosh Shilimkar
2017-01-23 9:58 ` Shawn Guo
2017-01-18 12:34 ` Arnd Bergmann [this message]
2017-01-18 13:07 ` [PATCH 0/2] ARM: DTS: Fix broken GICv2 register maps Marc Zyngier
2017-01-19 17:08 ` Tony Lindgren
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=2966702.djJyWhCMlK@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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