From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: zte: clean up gic-v3 redistributor properties
Date: Sat, 3 Dec 2016 13:08:05 +0000 [thread overview]
Message-ID: <20161203130805.61b1f85c@why.wild-wind.fr.eu.org> (raw)
In-Reply-To: <1480768600-20827-1-git-send-email-shawnguo@kernel.org>
On Sat, 3 Dec 2016 20:36:40 +0800
Shawn Guo <shawnguo@kernel.org> wrote:
> The gic-v3 property redistributor-stride is only meant as a workaround
> for broken platforms that have a redistributor stride deviating what the
> architecture defines, i.e. 128KiB for GICv3, 256KiB for GICv4. This is
> not the case for ZX296718, and redistributor-stride is not really
> necessary. Let's drop it.
>
> Also, #redistributor-regions is only required when there is more than
> one such region is present. Let's remove it as well.
>
> Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2016-12-03 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 12:36 [PATCH] arm64: dts: zte: clean up gic-v3 redistributor properties Shawn Guo
2016-12-03 13:08 ` Marc Zyngier [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=20161203130805.61b1f85c@why.wild-wind.fr.eu.org \
--to=marc.zyngier@arm.com \
--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