linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: linux@armlinux.org.uk, bp@alien8.de, mark.rutland@arm.com,
	robh+dt@kernel.org, mchehab@kernel.org, james.morse@arm.com,
	jlu@pengutronix.de, gregory.clement@bootlin.com
Cc: linux-arm-kernel@lists.infradead.org, linux-edac@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH v8 6/9] ARM: l2x0: add marvell,ecc-enable property for aurora
Date: Fri, 10 May 2019 22:15:33 +1200	[thread overview]
Message-ID: <20190510101536.6724-7-chris.packham@alliedtelesis.co.nz> (raw)
In-Reply-To: <20190510101536.6724-1-chris.packham@alliedtelesis.co.nz>

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@pengutronix.de: use aurora specific define AURORA_ACR_ECC_EN]
Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
---

Notes:
    Changes in v7:
    - remove marvell,ecc-disable

 arch/arm/mm/cache-l2x0.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/arch/arm/mm/cache-l2x0.c b/arch/arm/mm/cache-l2x0.c
index b70bee74750d..e5380f7b14a5 100644
--- a/arch/arm/mm/cache-l2x0.c
+++ b/arch/arm/mm/cache-l2x0.c
@@ -1505,6 +1505,11 @@ static void __init aurora_of_parse(const struct device_node *np,
 		mask |= AURORA_ACR_FORCE_WRITE_POLICY_MASK;
 	}
 
+	if (of_property_read_bool(np, "marvell,ecc-enable")) {
+		mask |= AURORA_ACR_ECC_EN;
+		val |= AURORA_ACR_ECC_EN;
+	}
+
 	if (of_property_read_bool(np, "arm,parity-enable")) {
 		mask |= AURORA_ACR_PARITY_EN;
 		val |= AURORA_ACR_PARITY_EN;
-- 
2.21.0


  parent reply	other threads:[~2019-05-10 10:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10 10:15 [PATCH v8 0/9] EDAC drivers for Armada XP L2 and DDR Chris Packham
2019-05-10 10:15 ` [PATCH v8 1/9] ARM: l2c: move cache-aurora-l2.h to asm/hardware Chris Packham
2019-05-10 10:15 ` [PATCH v8 2/9] ARM: aurora-l2: add prefix to MAX_RANGE_SIZE Chris Packham
2019-05-10 10:15 ` [PATCH v8 3/9] ARM: aurora-l2: add defines for parity and ECC registers Chris Packham
2019-05-10 10:15 ` [PATCH v8 4/9] ARM: l2x0: support parity-enable/disable on aurora Chris Packham
2019-05-10 10:15 ` [PATCH v8 5/9] dt-bindings: ARM: document marvell,ecc-enable binding Chris Packham
2019-05-10 10:15 ` Chris Packham [this message]
2019-05-10 10:15 ` [PATCH v8 7/9] EDAC: Add missing debugfs_create_x32 wrapper Chris Packham
2019-05-10 10:15 ` [PATCH v8 8/9] EDAC: Add driver for the Marvell Armada XP SDRAM and L2 cache ECC Chris Packham
2019-05-10 10:15 ` [PATCH v8 9/9] EDAC: armada_xp: Add support for more SoCs Chris Packham
2019-06-07  0:47 ` [PATCH v8 0/9] EDAC drivers for Armada XP L2 and DDR Chris Packham

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=20190510101536.6724-7-chris.packham@alliedtelesis.co.nz \
    --to=chris.packham@alliedtelesis.co.nz \
    --cc=bp@alien8.de \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=james.morse@arm.com \
    --cc=jlu@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=robh+dt@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).