From: Rob Herring <robh@kernel.org>
To: Yash Shah <yash.shah@sifive.com>
Cc: linux-riscv@lists.infradead.org, linux-edac@vger.kernel.org,
palmer@sifive.com, paul.walmsley@sifive.com,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
aou@eecs.berkeley.edu, bp@alien8.de, mchehab@kernel.org,
devicetree@vger.kernel.org
Subject: [1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller
Date: Thu, 28 Mar 2019 08:16:57 -0500 [thread overview]
Message-ID: <20190328131657.GA9056@bogus> (raw)
On Tue, Mar 12, 2019 at 02:51:00PM +0530, Yash Shah wrote:
> DT documentation for L2 cache controller added.
>
> Signed-off-by: Yash Shah <yash.shah@sifive.com>
> ---
> .../devicetree/bindings/edac/sifive-edac-l2.txt | 31 ++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/edac/sifive-edac-l2.txt
>
> diff --git a/Documentation/devicetree/bindings/edac/sifive-edac-l2.txt b/Documentation/devicetree/bindings/edac/sifive-edac-l2.txt
> new file mode 100644
> index 0000000..abce09f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/edac/sifive-edac-l2.txt
> @@ -0,0 +1,31 @@
> +SiFive L2 Cache EDAC driver device tree bindings
> +-------------------------------------------------
> +This driver uses the EDAC framework to report L2 cache controller ECC errors.
Bindings are for h/w blocks, not drivers. (And Boris may want a single
driver, but bindings should reflect the h/w, not what Linux (currently)
wants.
Are the only controls for ECC? Are all the cache attributes discoverable
(size, ways, line size, level, etc.)?
> +
> +- compatible: Should be "sifive,<chip>-ccache" and "sifive,ccache<version>".
> + Supported compatible strings are:
> + "sifive,fu540-c000-ccache" for the SiFive cache controller v0 as integrated
> + onto the SiFive FU540 chip, and "sifive,ccache0" for the SiFive
> + cache controller v0 IP block with no chip integration tweaks.
> + Please refer to sifive-blocks-ip-versioning.txt for details
> +
> +- interrupts: Must contain 3 entries for FU540 (DirError, DataError, and
> + DataFail signals) or 4 entries for other chips (DirError, DirFail, DataError,
> + and DataFail signals)
3 or 4, but you only have 1 chip compatible defined?
> +
> +- interrupt-parent: Must be core interrupt controller
This is implied and could be in a parent node.
> +
> +- reg: Physical base address and size of L2 cache controller registers map
> + A second range can indicate L2 Loosely Integrated Memory
> +
> +- reg-names: Names for the cells of reg, must contain "control" and "sideband"
> +
> +Example:
> +
> +cache-controller@2010000 {
> + compatible = "sifive,fu540-c000-ccache", "sifive,ccache0";
> + interrupt-parent = <&plic>;
> + interrupts = <1 2 3>;
> + reg = <0x0 0x2010000 0x0 0x1000 0x0 0x8000000 0x0 0x2000000>;
> + reg-names = "control", "sideband";
> +};
> --
> 1.9.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Yash Shah <yash.shah@sifive.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
aou@eecs.berkeley.edu, palmer@sifive.com,
linux-kernel@vger.kernel.org, bp@alien8.de,
paul.walmsley@sifive.com, linux-riscv@lists.infradead.org,
mchehab@kernel.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH 1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller
Date: Thu, 28 Mar 2019 08:16:57 -0500 [thread overview]
Message-ID: <20190328131657.GA9056@bogus> (raw)
In-Reply-To: <1552382461-13051-2-git-send-email-yash.shah@sifive.com>
On Tue, Mar 12, 2019 at 02:51:00PM +0530, Yash Shah wrote:
> DT documentation for L2 cache controller added.
>
> Signed-off-by: Yash Shah <yash.shah@sifive.com>
> ---
> .../devicetree/bindings/edac/sifive-edac-l2.txt | 31 ++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/edac/sifive-edac-l2.txt
>
> diff --git a/Documentation/devicetree/bindings/edac/sifive-edac-l2.txt b/Documentation/devicetree/bindings/edac/sifive-edac-l2.txt
> new file mode 100644
> index 0000000..abce09f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/edac/sifive-edac-l2.txt
> @@ -0,0 +1,31 @@
> +SiFive L2 Cache EDAC driver device tree bindings
> +-------------------------------------------------
> +This driver uses the EDAC framework to report L2 cache controller ECC errors.
Bindings are for h/w blocks, not drivers. (And Boris may want a single
driver, but bindings should reflect the h/w, not what Linux (currently)
wants.
Are the only controls for ECC? Are all the cache attributes discoverable
(size, ways, line size, level, etc.)?
> +
> +- compatible: Should be "sifive,<chip>-ccache" and "sifive,ccache<version>".
> + Supported compatible strings are:
> + "sifive,fu540-c000-ccache" for the SiFive cache controller v0 as integrated
> + onto the SiFive FU540 chip, and "sifive,ccache0" for the SiFive
> + cache controller v0 IP block with no chip integration tweaks.
> + Please refer to sifive-blocks-ip-versioning.txt for details
> +
> +- interrupts: Must contain 3 entries for FU540 (DirError, DataError, and
> + DataFail signals) or 4 entries for other chips (DirError, DirFail, DataError,
> + and DataFail signals)
3 or 4, but you only have 1 chip compatible defined?
> +
> +- interrupt-parent: Must be core interrupt controller
This is implied and could be in a parent node.
> +
> +- reg: Physical base address and size of L2 cache controller registers map
> + A second range can indicate L2 Loosely Integrated Memory
> +
> +- reg-names: Names for the cells of reg, must contain "control" and "sideband"
> +
> +Example:
> +
> +cache-controller@2010000 {
> + compatible = "sifive,fu540-c000-ccache", "sifive,ccache0";
> + interrupt-parent = <&plic>;
> + interrupts = <1 2 3>;
> + reg = <0x0 0x2010000 0x0 0x1000 0x0 0x8000000 0x0 0x2000000>;
> + reg-names = "control", "sideband";
> +};
> --
> 1.9.1
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Yash Shah <yash.shah@sifive.com>
Cc: linux-riscv@lists.infradead.org, linux-edac@vger.kernel.org,
palmer@sifive.com, paul.walmsley@sifive.com,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
aou@eecs.berkeley.edu, bp@alien8.de, mchehab@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller
Date: Thu, 28 Mar 2019 08:16:57 -0500 [thread overview]
Message-ID: <20190328131657.GA9056@bogus> (raw)
In-Reply-To: <1552382461-13051-2-git-send-email-yash.shah@sifive.com>
On Tue, Mar 12, 2019 at 02:51:00PM +0530, Yash Shah wrote:
> DT documentation for L2 cache controller added.
>
> Signed-off-by: Yash Shah <yash.shah@sifive.com>
> ---
> .../devicetree/bindings/edac/sifive-edac-l2.txt | 31 ++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/edac/sifive-edac-l2.txt
>
> diff --git a/Documentation/devicetree/bindings/edac/sifive-edac-l2.txt b/Documentation/devicetree/bindings/edac/sifive-edac-l2.txt
> new file mode 100644
> index 0000000..abce09f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/edac/sifive-edac-l2.txt
> @@ -0,0 +1,31 @@
> +SiFive L2 Cache EDAC driver device tree bindings
> +-------------------------------------------------
> +This driver uses the EDAC framework to report L2 cache controller ECC errors.
Bindings are for h/w blocks, not drivers. (And Boris may want a single
driver, but bindings should reflect the h/w, not what Linux (currently)
wants.
Are the only controls for ECC? Are all the cache attributes discoverable
(size, ways, line size, level, etc.)?
> +
> +- compatible: Should be "sifive,<chip>-ccache" and "sifive,ccache<version>".
> + Supported compatible strings are:
> + "sifive,fu540-c000-ccache" for the SiFive cache controller v0 as integrated
> + onto the SiFive FU540 chip, and "sifive,ccache0" for the SiFive
> + cache controller v0 IP block with no chip integration tweaks.
> + Please refer to sifive-blocks-ip-versioning.txt for details
> +
> +- interrupts: Must contain 3 entries for FU540 (DirError, DataError, and
> + DataFail signals) or 4 entries for other chips (DirError, DirFail, DataError,
> + and DataFail signals)
3 or 4, but you only have 1 chip compatible defined?
> +
> +- interrupt-parent: Must be core interrupt controller
This is implied and could be in a parent node.
> +
> +- reg: Physical base address and size of L2 cache controller registers map
> + A second range can indicate L2 Loosely Integrated Memory
> +
> +- reg-names: Names for the cells of reg, must contain "control" and "sideband"
> +
> +Example:
> +
> +cache-controller@2010000 {
> + compatible = "sifive,fu540-c000-ccache", "sifive,ccache0";
> + interrupt-parent = <&plic>;
> + interrupts = <1 2 3>;
> + reg = <0x0 0x2010000 0x0 0x1000 0x0 0x8000000 0x0 0x2000000>;
> + reg-names = "control", "sideband";
> +};
> --
> 1.9.1
>
next reply other threads:[~2019-03-28 13:16 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 13:16 Rob Herring [this message]
2019-03-28 13:16 ` [PATCH 1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller Rob Herring
2019-03-28 13:16 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2019-04-04 1:17 [1/2] " Rob Herring
2019-04-04 1:17 ` [PATCH 1/2] " Rob Herring
2019-04-04 1:17 ` Rob Herring
2019-04-04 1:04 [1/2] " Rob Herring
2019-04-04 1:04 ` [PATCH 1/2] " Rob Herring
2019-04-04 1:04 ` Rob Herring
2019-04-01 16:36 [1/2] " James Morse
2019-04-01 16:36 ` [PATCH 1/2] " James Morse
2019-04-01 16:36 ` James Morse
2019-03-29 20:24 [1/2] " Borislav Petkov
2019-03-29 20:24 ` [PATCH 1/2] " Borislav Petkov
2019-03-29 20:24 ` Borislav Petkov
2019-03-29 19:41 [1/2] " Rob Herring
2019-03-29 19:41 ` [PATCH 1/2] " Rob Herring
2019-03-29 19:41 ` Rob Herring
2019-03-29 14:27 [1/2] " Borislav Petkov
2019-03-29 14:27 ` [PATCH 1/2] " Borislav Petkov
2019-03-29 14:27 ` Borislav Petkov
2019-03-29 14:11 [1/2] " Rob Herring
2019-03-29 14:11 ` [PATCH 1/2] " Rob Herring
2019-03-29 14:11 ` Rob Herring
2019-03-28 18:47 [1/2] " James Morse
2019-03-28 18:47 ` [PATCH 1/2] " James Morse
2019-03-28 18:47 ` James Morse
2019-03-25 21:47 [2/2] sifive: edac: Add EDAC driver for Sifive l2 Cache Controller Borislav Petkov
2019-03-25 21:47 ` [PATCH 2/2] " Borislav Petkov
2019-03-25 21:47 ` Borislav Petkov
2019-03-25 21:18 [2/2] " Paul Walmsley
2019-03-25 21:18 ` [PATCH 2/2] " Paul Walmsley
2019-03-25 21:18 ` Paul Walmsley
2019-03-25 6:54 [2/2] " Borislav Petkov
2019-03-25 6:54 ` [PATCH 2/2] " Borislav Petkov
2019-03-25 6:54 ` Borislav Petkov
2019-03-25 0:16 [2/2] " Paul Walmsley
2019-03-25 0:16 ` [PATCH 2/2] " Paul Walmsley
2019-03-25 0:16 ` Paul Walmsley
2019-03-12 16:31 [2/2] " Paul Walmsley
2019-03-12 16:31 ` [PATCH 2/2] " Paul Walmsley
2019-03-12 16:31 ` Paul Walmsley
2019-03-12 9:28 [2/2] " Borislav Petkov
2019-03-12 9:28 ` [PATCH 2/2] " Borislav Petkov
2019-03-12 9:28 ` Borislav Petkov
2019-03-12 9:21 [2/2] " Yash Shah
2019-03-12 9:21 ` [PATCH 2/2] " Yash Shah
2019-03-12 9:21 ` Yash Shah
2019-03-12 9:21 [1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller Yash Shah
2019-03-12 9:21 ` [PATCH 1/2] " Yash Shah
2019-03-12 9:21 ` Yash Shah
2019-03-12 9:20 [PATCH 0/2] L2 Cache EDAC Support for HiFive Unleashed Yash Shah
2019-03-12 9:20 ` Yash Shah
2019-03-12 9:20 ` Yash Shah
2019-03-12 16:32 ` Paul Walmsley
2019-03-12 16:32 ` Paul Walmsley
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=20190328131657.GA9056@bogus \
--to=robh@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=yash.shah@sifive.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.