From: Dirk Behme <dirk.behme@gmail.com>
To: linux-sh@vger.kernel.org, horms@verge.net.au, geert+renesas@glider.be
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: dts: r8a7795: Add L2 cache-controller nodes
Date: Wed, 3 Feb 2016 18:21:17 +0100 [thread overview]
Message-ID: <56B2370D.2010102@gmail.com> (raw)
In-Reply-To: <1452953856-5146-1-git-send-email-dirk.behme@gmail.com>
On 16.01.2016 15:17, Dirk Behme wrote:
> From: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Add device nodes for the L2 caches, and link the CPU node to its L2
> cache node.
>
> The L2 cache for the Cortex-A57 CPU cores is 2 MiB large (organized as
> 128 KiB x 16 ways).
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
> ---
> Changes in v2: Dropped the not yet merged Cortex A53 part.
>
> arch/arm64/boot/dts/renesas/r8a7795.dtsi | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> index a82bce8..a22ae65 100644
> --- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> @@ -39,6 +39,7 @@
> compatible = "arm,cortex-a57", "arm,armv8";
> reg = <0x0>;
> device_type = "cpu";
> + next-level-cache = <&L2_CA57>;
> enable-method = "psci";
> };
>
> @@ -46,22 +47,29 @@
> compatible = "arm,cortex-a57","arm,armv8";
> reg = <0x1>;
> device_type = "cpu";
> + next-level-cache = <&L2_CA57>;
> enable-method = "psci";
> };
> a57_2: cpu@2 {
> compatible = "arm,cortex-a57","arm,armv8";
> reg = <0x2>;
> device_type = "cpu";
> + next-level-cache = <&L2_CA57>;
> enable-method = "psci";
> };
> a57_3: cpu@3 {
> compatible = "arm,cortex-a57","arm,armv8";
> reg = <0x3>;
> device_type = "cpu";
> + next-level-cache = <&L2_CA57>;
> enable-method = "psci";
> };
> };
>
> + L2_CA57: cache-controller@0 {
> + compatible = "cache";
> + };
> +
> extal_clk: extal {
> compatible = "fixed-clock";
> #clock-cells = <0>;
>
Any further comments to this? If not, could this be applied?
Best regards
Dirk
next prev parent reply other threads:[~2016-02-03 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 14:17 [PATCH v2] arm64: dts: r8a7795: Add L2 cache-controller nodes Dirk Behme
2016-02-03 17:21 ` Dirk Behme [this message]
[not found] ` <56B2370D.2010102-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-05 9:57 ` Simon Horman
2016-02-08 8:42 ` Geert Uytterhoeven
[not found] ` <CAMuHMdVRhwGh2bvfNSguX0XnMW0eEgLRTCt3Y3-+KfV0Jy9WHw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-08 8:54 ` Dirk Behme
2016-02-08 9:01 ` Geert Uytterhoeven
2016-02-08 17:08 ` Dirk Behme
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=56B2370D.2010102@gmail.com \
--to=dirk.behme@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.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).