From: Sudeep.KarkadaNagesha@arm.com (Sudeep KarkadaNagesha)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: dove: add cpu device tree node
Date: Mon, 29 Jul 2013 13:41:49 +0100 [thread overview]
Message-ID: <51F6630D.5010603@arm.com> (raw)
In-Reply-To: <1375100946-28521-2-git-send-email-sebastian.hesselbarth@gmail.com>
On 29/07/13 13:29, Sebastian Hesselbarth wrote:
> This adds a node for the Marvell Sheeva PJ4A CPU found on Dove SoCs.
> While at it, also move the l2-cache node out of internal registers and
> consistently name different nodes.
>
> Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> ---
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Jason Cooper <jason@lakedaemon.net>
> Cc: Andrew Lunn <andrew@lunn.ch>
> Cc: linux-arm-kernel at lists.infradead.org
> Cc: devicetree at vger.kernel.org
> Cc: linux-kernel at vger.kernel.org
> ---
> arch/arm/boot/dts/dove.dtsi | 52 ++++++++++++++++++++++++++-----------------
> 1 file changed, 32 insertions(+), 20 deletions(-)
>
> diff --git a/arch/arm/boot/dts/dove.dtsi b/arch/arm/boot/dts/dove.dtsi
> index 8d5be1e8..09d9710 100644
> --- a/arch/arm/boot/dts/dove.dtsi
> +++ b/arch/arm/boot/dts/dove.dtsi
> @@ -10,6 +10,23 @@
> gpio2 = &gpio2;
> };
>
> + cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + cpu0: cpu at 0 {
> + compatible = "marvell,pj4a", "marvell,sheeva-v7";
> + device_type = "cpu";
> + next-level-cache = <&l2>;
> + reg = <0>;
> + };
> + };
> +
> + l2: l2-cache {
> + compatible = "marvell,tauros2-cache";
> + marvell,tauros2-cache-features = <0>;
> + };
Hi Sebastian,
This is not entirely related to the patch but thought of checking with
you. I was trying to get info on L2 cache controller on Marvell SoCs,
mainly structure or way/set size. Is that something we can get
dynamically ? Some specification I referred said its integrated and some
said its separate(not unified). Basically I need information around
various L2 cache implementations(Tauros2/Feroceon) from Marvell.
Any pointers or contacts to get this information will be helpful.
Regards,
Sudeep
next prev parent reply other threads:[~2013-07-29 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 12:29 [PATCH 0/4] ARM: dove: DT updates for v3.11-rc2 Sebastian Hesselbarth
2013-07-29 12:29 ` [PATCH 1/4] ARM: dove: add cpu device tree node Sebastian Hesselbarth
2013-07-29 12:41 ` Sudeep KarkadaNagesha [this message]
2013-07-29 14:10 ` Sebastian Hesselbarth
2013-07-29 12:29 ` [PATCH 2/4] ARM: dove: add common pinmux functions to DT Sebastian Hesselbarth
2013-07-29 12:29 ` [PATCH 3/4] ARM: dove: add GPIO IR receiver node to SolidRun CuBox Sebastian Hesselbarth
2013-07-29 12:29 ` [PATCH 4/4] ARM: dove: add initial DT file for Globalscale D2Plug Sebastian Hesselbarth
2013-07-29 18:45 ` Andrew Lunn
2013-07-30 8:03 ` Sebastian Hesselbarth
2013-07-30 8:40 ` Andrew Lunn
2013-08-03 18:03 ` [PATCH 0/4] ARM: dove: DT updates for v3.11-rc2 Jason Cooper
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=51F6630D.5010603@arm.com \
--to=sudeep.karkadanagesha@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).