linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.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:58:50 +0000	[thread overview]
Message-ID: <5667286A.5010901@arm.com> (raw)
In-Reply-To: <5667267E.2080601@gmail.com>



On 08/12/15 18:50, Dirk Behme wrote:
> 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

A15 and A7 are 32-bit cores, so you can't generalize it.
IMO you can just specify that this binding is applicable for separate L2
cache controllers.

-- 
-- 
Regards,
Sudeep

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

Thread overview: 20+ 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 ` [PATCH v2 1/6] ARM: shmobile: r8a73a4 dtsi: " Geert Uytterhoeven
2015-12-07 18:24 ` [PATCH v2 2/6] ARM: shmobile: r8a7790 " 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 ` [PATCH v2 4/6] ARM: shmobile: r8a7793 " Geert Uytterhoeven
2015-12-07 18:24 ` [PATCH v2 5/6] ARM: shmobile: r8a7794 " 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:49   ` Sudeep Holla
2015-12-07 19:03     ` Mark Rutland
2015-12-07 20:18       ` Geert Uytterhoeven
2015-12-15  8:45         ` Geert Uytterhoeven
2015-12-08 18:50       ` Dirk Behme
2015-12-08 18:58         ` Sudeep Holla [this message]
2015-12-08 19:16         ` Mark Rutland
2015-12-09 16:58           ` Dirk Behme
2015-12-09 17:16             ` Sudeep Holla
2015-12-09 17:21             ` Mark Rutland
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 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=5667286A.5010901@arm.com \
    --to=sudeep.holla@arm.com \
    --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;
as well as URLs for NNTP newsgroup(s).