From: Mark Rutland <mark.rutland@arm.com>
To: 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: Mon, 7 Dec 2015 19:03:55 +0000 [thread overview]
Message-ID: <20151207190355.GE28024@leverpostej> (raw)
In-Reply-To: <5665D4C7.1050705@arm.com>
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.
Thanks,
Mark.
next prev parent reply other threads:[~2015-12-07 19:03 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
[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 ` [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 [this message]
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
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=20151207190355.GE28024@leverpostej \
--to=mark.rutland@arm.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=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 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).