From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 5/8] ARM: l2x0: add marvell,ecc-enable property for aurora
Date: Fri, 19 Jan 2018 15:28:36 -0600 [thread overview]
Message-ID: <20180119212836.r76seqe5dx6xim3w@rob-hp-laptop> (raw)
In-Reply-To: <20180112012755.20495-6-chris.packham@alliedtelesis.co.nz>
On Fri, Jan 12, 2018 at 02:27:52PM +1300, Chris Packham wrote:
> The aurora cache on the Marvell Armada-XP SoC supports ECC protection
> for the L2 data arrays. Add a "marvell,ecc-enable" device tree property
> which can be used to enable this.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> [jlu at pengutronix.de: use aurora specific define AURORA_ACR_ECC_EN]
> Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
> ---
> Documentation/devicetree/bindings/arm/l2c2x0.txt | 2 ++
> arch/arm/mm/cache-l2x0.c | 7 +++++++
> 2 files changed, 9 insertions(+)
The Calxeda PL310 has ECC too so maybe shouldn't have a vendor prefix,
but I don't think anyone will ever care to change it at this point.
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-01-19 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180112012755.20495-1-chris.packham@alliedtelesis.co.nz>
2018-01-12 1:27 ` [PATCH v4 1/8] ARM: l2c: move cache-aurora-l2.h to asm/hardware Chris Packham
2018-01-12 1:27 ` [PATCH v4 2/8] ARM: aurora-l2: add prefix to MAX_RANGE_SIZE Chris Packham
2018-01-12 1:27 ` [PATCH v4 3/8] ARM: aurora-l2: add defines for parity and ECC registers Chris Packham
2018-01-12 1:27 ` [PATCH v4 4/8] ARM: l2x0: support parity-enable/disable on aurora Chris Packham
2018-01-12 1:27 ` [PATCH v4 5/8] ARM: l2x0: add marvell,ecc-enable property for aurora Chris Packham
2018-01-19 21:28 ` Rob Herring [this message]
[not found] ` <1525338355.17782.21.camel@pengutronix.de>
2018-05-03 20:54 ` [PATCH v4 0/8] EDAC drivers for Armada XP L2 and DDR Chris Packham
2018-10-09 7:06 ` Uwe Kleine-König
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=20180119212836.r76seqe5dx6xim3w@rob-hp-laptop \
--to=robh@kernel.org \
--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