All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@gmail.com>
To: Mark Rutland <mark.rutland@arm.com>, Sudeep Holla <sudeep.holla@arm.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Lina Iyer <lina.iyer@linaro.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-sh@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 6/6] arm64: renesas: r8a7795: Add L2 cache-controller nodes
Date: Tue, 8 Dec 2015 19:50:38 +0100	[thread overview]
Message-ID: <5667267E.2080601@gmail.com> (raw)
In-Reply-To: <20151207190355.GE28024@leverpostej>

On 07.12.2015 20:03, Mark Rutland wrote:
> On Mon, Dec 07, 2015 at 06:49:43PM +0000, Sudeep Holla wrote:
>>
>> On 07/12/15 18:24, Geert Uytterhoeven wrote:
>>> +	L2_CA57: cache-controller@0 {
>>> +		compatible = "cache";
>>> +		arm,data-latency = <4 4 1>;
>>> +		arm,tag-latency = <3 3 3>;
>>
>> Interesting, only PL2xx/3xx cache controller driver reads this from the
>> DT and configures the controller. The integrated L2 found in
>> A15/A7/A57/A53 needs doesn't make use of these values from the DT.
>
> These properties seem to be from l2cc.txt, which really only corresponds
> to PL210/PL220/PL310 (and variants) and isn't as generic as it sounds.
>
> I don't see that these are necessary at all.


What's about a documentation patch like [1], then?


For what is the arm64 dts entry

cpu@0 {
	...
	next-level-cache = <&L2_0>;
};

L2_0: l2-cache0 {
	compatible = "cache";
};

good for at all, then?


Best regards

Dirk


[1]

diff --git a/Documentation/devicetree/bindings/arm/l2cc.txt 
b/Documentation/devicetree/bindings/arm/l2cc.txt
index 06c88a4..f687aed 100644
--- a/Documentation/devicetree/bindings/arm/l2cc.txt
+++ b/Documentation/devicetree/bindings/arm/l2cc.txt
@@ -1,12 +1,18 @@
  * ARM L2 Cache Controller

-ARM cores often have a separate level 2 cache controller. There are 
various
+ARM 32-bit cores often have a separate level 2 cache controller. 
There are various
  implementations of the L2 cache controller with compatible 
programming models.
  Some of the properties that are just prefixed "cache-*" are taken 
from section
  3.7.3 of the ePAPR v1.1 specification which can be found at:
 
https://www.power.org/wp-content/uploads/2012/06/Power_ePAPR_APPROVED_v1.1.pdf

-The ARM L2 cache representation in the device tree should be done as 
follows:
+ARM 64-bit cores (e.g. A15/A7/A57/A53) have an integrated level 2 
cache which
+doesn't make use of any values from the kernel device tree. There is no
+L2 cache configuration done in the kernel. The L2 cache is assumed to be
+preconfigured by early secure boot code.
+
+The ARM L2 cache representation for 32-bit cores in the device tree 
should be done
+as follows:

  Required properties:



WARNING: multiple messages have this Message-ID (diff)
From: Dirk Behme <dirk.behme@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 6/6] arm64: renesas: r8a7795: Add L2 cache-controller nodes
Date: Tue, 08 Dec 2015 18:50:38 +0000	[thread overview]
Message-ID: <5667267E.2080601@gmail.com> (raw)
In-Reply-To: <20151207190355.GE28024@leverpostej>

On 07.12.2015 20:03, Mark Rutland wrote:
> On Mon, Dec 07, 2015 at 06:49:43PM +0000, Sudeep Holla wrote:
>>
>> On 07/12/15 18:24, Geert Uytterhoeven wrote:
>>> +	L2_CA57: cache-controller@0 {
>>> +		compatible = "cache";
>>> +		arm,data-latency = <4 4 1>;
>>> +		arm,tag-latency = <3 3 3>;
>>
>> Interesting, only PL2xx/3xx cache controller driver reads this from the
>> DT and configures the controller. The integrated L2 found in
>> A15/A7/A57/A53 needs doesn't make use of these values from the DT.
>
> These properties seem to be from l2cc.txt, which really only corresponds
> to PL210/PL220/PL310 (and variants) and isn't as generic as it sounds.
>
> I don't see that these are necessary at all.


What's about a documentation patch like [1], then?


For what is the arm64 dts entry

cpu@0 {
	...
	next-level-cache = <&L2_0>;
};

L2_0: l2-cache0 {
	compatible = "cache";
};

good for at all, then?


Best regards

Dirk


[1]

diff --git a/Documentation/devicetree/bindings/arm/l2cc.txt 
b/Documentation/devicetree/bindings/arm/l2cc.txt
index 06c88a4..f687aed 100644
--- a/Documentation/devicetree/bindings/arm/l2cc.txt
+++ b/Documentation/devicetree/bindings/arm/l2cc.txt
@@ -1,12 +1,18 @@
  * ARM L2 Cache Controller

-ARM cores often have a separate level 2 cache controller. There are 
various
+ARM 32-bit cores often have a separate level 2 cache controller. 
There are various
  implementations of the L2 cache controller with compatible 
programming models.
  Some of the properties that are just prefixed "cache-*" are taken 
from section
  3.7.3 of the ePAPR v1.1 specification which can be found at:
 
https://www.power.org/wp-content/uploads/2012/06/Power_ePAPR_APPROVED_v1.1.pdf

-The ARM L2 cache representation in the device tree should be done as 
follows:
+ARM 64-bit cores (e.g. A15/A7/A57/A53) have an integrated level 2 
cache which
+doesn't make use of any values from the kernel device tree. There is no
+L2 cache configuration done in the kernel. The L2 cache is assumed to be
+preconfigured by early secure boot code.
+
+The ARM L2 cache representation for 32-bit cores in the device tree 
should be done
+as follows:

  Required properties:



WARNING: multiple messages have this Message-ID (diff)
From: dirk.behme@gmail.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 6/6] arm64: renesas: r8a7795: Add L2 cache-controller nodes
Date: Tue, 8 Dec 2015 19:50:38 +0100	[thread overview]
Message-ID: <5667267E.2080601@gmail.com> (raw)
In-Reply-To: <20151207190355.GE28024@leverpostej>

On 07.12.2015 20:03, Mark Rutland wrote:
> On Mon, Dec 07, 2015 at 06:49:43PM +0000, Sudeep Holla wrote:
>>
>> On 07/12/15 18:24, Geert Uytterhoeven wrote:
>>> +	L2_CA57: cache-controller at 0 {
>>> +		compatible = "cache";
>>> +		arm,data-latency = <4 4 1>;
>>> +		arm,tag-latency = <3 3 3>;
>>
>> Interesting, only PL2xx/3xx cache controller driver reads this from the
>> DT and configures the controller. The integrated L2 found in
>> A15/A7/A57/A53 needs doesn't make use of these values from the DT.
>
> These properties seem to be from l2cc.txt, which really only corresponds
> to PL210/PL220/PL310 (and variants) and isn't as generic as it sounds.
>
> I don't see that these are necessary at all.


What's about a documentation patch like [1], then?


For what is the arm64 dts entry

cpu at 0 {
	...
	next-level-cache = <&L2_0>;
};

L2_0: l2-cache0 {
	compatible = "cache";
};

good for at all, then?


Best regards

Dirk


[1]

diff --git a/Documentation/devicetree/bindings/arm/l2cc.txt 
b/Documentation/devicetree/bindings/arm/l2cc.txt
index 06c88a4..f687aed 100644
--- a/Documentation/devicetree/bindings/arm/l2cc.txt
+++ b/Documentation/devicetree/bindings/arm/l2cc.txt
@@ -1,12 +1,18 @@
  * ARM L2 Cache Controller

-ARM cores often have a separate level 2 cache controller. There are 
various
+ARM 32-bit cores often have a separate level 2 cache controller. 
There are various
  implementations of the L2 cache controller with compatible 
programming models.
  Some of the properties that are just prefixed "cache-*" are taken 
from section
  3.7.3 of the ePAPR v1.1 specification which can be found at:
 
https://www.power.org/wp-content/uploads/2012/06/Power_ePAPR_APPROVED_v1.1.pdf

-The ARM L2 cache representation in the device tree should be done as 
follows:
+ARM 64-bit cores (e.g. A15/A7/A57/A53) have an integrated level 2 
cache which
+doesn't make use of any values from the kernel device tree. There is no
+L2 cache configuration done in the kernel. The L2 cache is assumed to be
+preconfigured by early secure boot code.
+
+The ARM L2 cache representation for 32-bit cores in the device tree 
should be done
+as follows:

  Required properties:

  parent reply	other threads:[~2015-12-08 18:50 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 18:24 [PATCH v2 0/6] ARM/arm64 : shmobile/renesas: Add L2 cache-controller nodes Geert Uytterhoeven
2015-12-07 18:24 ` Geert Uytterhoeven
2015-12-07 18:24 ` Geert Uytterhoeven
2015-12-07 18:24 ` [PATCH v2 1/6] ARM: shmobile: r8a73a4 dtsi: " Geert Uytterhoeven
2015-12-07 18:24   ` Geert Uytterhoeven
2015-12-07 18:24   ` Geert Uytterhoeven
2015-12-07 18:24 ` [PATCH v2 2/6] ARM: shmobile: r8a7790 " Geert Uytterhoeven
2015-12-07 18:24   ` Geert Uytterhoeven
2015-12-07 18:24   ` Geert Uytterhoeven
2015-12-07 18:24 ` [PATCH v2 3/6] ARM: shmobile: r8a7791 dtsi: Add L2 cache-controller node Geert Uytterhoeven
2015-12-07 18:24   ` Geert Uytterhoeven
2015-12-07 18:24   ` Geert Uytterhoeven
2015-12-07 18:24 ` [PATCH v2 4/6] ARM: shmobile: r8a7793 " Geert Uytterhoeven
2015-12-07 18:24   ` Geert Uytterhoeven
2015-12-07 18:24   ` Geert Uytterhoeven
     [not found] ` <1449512659-16688-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2015-12-07 18:24   ` [PATCH v2 5/6] ARM: shmobile: r8a7794 " Geert Uytterhoeven
2015-12-07 18:24     ` Geert Uytterhoeven
2015-12-07 18:24     ` Geert Uytterhoeven
2015-12-07 18:24 ` [PATCH v2 6/6] arm64: renesas: r8a7795: Add L2 cache-controller nodes Geert Uytterhoeven
2015-12-07 18:24   ` Geert Uytterhoeven
2015-12-07 18:24   ` Geert Uytterhoeven
2015-12-07 18:49   ` Sudeep Holla
2015-12-07 18:49     ` Sudeep Holla
2015-12-07 18:49     ` Sudeep Holla
2015-12-07 19:03     ` Mark Rutland
2015-12-07 19:03       ` Mark Rutland
2015-12-07 19:03       ` Mark Rutland
2015-12-07 20:18       ` Geert Uytterhoeven
2015-12-07 20:18         ` Geert Uytterhoeven
2015-12-07 20:18         ` Geert Uytterhoeven
2015-12-15  8:45         ` Geert Uytterhoeven
2015-12-15  8:45           ` Geert Uytterhoeven
2015-12-15  8:45           ` Geert Uytterhoeven
2015-12-08 18:50       ` Dirk Behme [this message]
2015-12-08 18:50         ` Dirk Behme
2015-12-08 18:50         ` Dirk Behme
2015-12-08 18:58         ` Sudeep Holla
2015-12-08 18:58           ` Sudeep Holla
2015-12-08 18:58           ` Sudeep Holla
2015-12-08 19:16         ` Mark Rutland
2015-12-08 19:16           ` Mark Rutland
2015-12-08 19:16           ` Mark Rutland
2015-12-09 16:58           ` Dirk Behme
2015-12-09 16:58             ` Dirk Behme
2015-12-09 16:58             ` Dirk Behme
2015-12-09 17:16             ` Sudeep Holla
2015-12-09 17:16               ` Sudeep Holla
2015-12-09 17:16               ` Sudeep Holla
2015-12-09 17:21             ` Mark Rutland
2015-12-09 17:21               ` Mark Rutland
2015-12-09 17:21               ` Mark Rutland
2015-12-09 17:34               ` Sudeep Holla
2015-12-09 17:34                 ` Sudeep Holla
2015-12-09 17:34                 ` Sudeep Holla
2016-02-15  1:58 ` [PATCH v2 0/6] ARM/arm64 : shmobile/renesas: " Simon Horman
2016-02-15  1:58   ` Simon Horman
2016-02-15  1:58   ` Simon Horman
2016-02-15 10:15   ` Geert Uytterhoeven
2016-02-15 10:15     ` Geert Uytterhoeven
2016-02-15 10:15     ` Geert Uytterhoeven

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=5667267E.2080601@gmail.com \
    --to=dirk.behme@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lina.iyer@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=will.deacon@arm.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.