From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support
Date: Mon, 2 May 2011 17:52:25 +0200 [thread overview]
Message-ID: <201105021752.25273.arnd@arndb.de> (raw)
In-Reply-To: <4DBEB1A8.3040202@gmail.com>
On Monday 02 May 2011, Rob Herring wrote:
> The SCU is accessed before ioremap is up. The only reason it is accessed
> early is to determine the number of cores present.
The number of cores should definitely be available in the device tree,
normally by looking at the root interrupt controller.
> The L2 can certainly be ioremapped and probed via DT. How about
> something like this:
>
> l2cc {
> compatible = "arm,pl310-l2";
> reg = <0xfff12000 0x1000>;
> aux-value = <0>;
> aux-mask = <0xffffffff>;
> };
sounds good to me.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robherring2@gmail.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
linux-arm-kernel@lists.infradead.org,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Russell King <linux@arm.linux.org.uk>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support
Date: Mon, 2 May 2011 17:52:25 +0200 [thread overview]
Message-ID: <201105021752.25273.arnd@arndb.de> (raw)
In-Reply-To: <4DBEB1A8.3040202@gmail.com>
On Monday 02 May 2011, Rob Herring wrote:
> The SCU is accessed before ioremap is up. The only reason it is accessed
> early is to determine the number of cores present.
The number of cores should definitely be available in the device tree,
normally by looking at the root interrupt controller.
> The L2 can certainly be ioremapped and probed via DT. How about
> something like this:
>
> l2cc {
> compatible = "arm,pl310-l2";
> reg = <0xfff12000 0x1000>;
> aux-value = <0>;
> aux-mask = <0xffffffff>;
> };
sounds good to me.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Nicolas Pitre
<nicolas.pitre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support
Date: Mon, 2 May 2011 17:52:25 +0200 [thread overview]
Message-ID: <201105021752.25273.arnd@arndb.de> (raw)
In-Reply-To: <4DBEB1A8.3040202-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Monday 02 May 2011, Rob Herring wrote:
> The SCU is accessed before ioremap is up. The only reason it is accessed
> early is to determine the number of cores present.
The number of cores should definitely be available in the device tree,
normally by looking at the root interrupt controller.
> The L2 can certainly be ioremapped and probed via DT. How about
> something like this:
>
> l2cc {
> compatible = "arm,pl310-l2";
> reg = <0xfff12000 0x1000>;
> aux-value = <0>;
> aux-mask = <0xffffffff>;
> };
sounds good to me.
Arnd
next prev parent reply other threads:[~2011-05-02 15:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 5:07 [RFC PATCH 0/4] ARM: Basic Xilinx Support Grant Likely
2011-05-02 5:07 ` Grant Likely
2011-05-02 5:07 ` [RFC PATCH 1/4] arm/dt: Add dt machine definition Grant Likely
2011-05-02 5:07 ` Grant Likely
2011-05-02 5:07 ` [RFC PATCH 2/4] of/address: Add of_find_matching_node_by_address helper Grant Likely
2011-05-02 5:07 ` Grant Likely
2011-05-02 5:07 ` [RFC PATCH 3/4] dt/irq: add of_irq_domain_add_simple() helper Grant Likely
2011-05-02 5:07 ` Grant Likely
2011-05-02 5:08 ` [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support Grant Likely
2011-05-02 5:08 ` Grant Likely
2011-05-02 7:06 ` Michal Simek
2011-05-02 7:06 ` Michal Simek
2011-05-02 7:06 ` Michal Simek
2011-05-02 8:39 ` Arnd Bergmann
2011-05-02 8:39 ` Arnd Bergmann
2011-05-02 13:29 ` Rob Herring
2011-05-02 13:29 ` Rob Herring
2011-05-02 13:29 ` Rob Herring
2011-05-02 15:52 ` Arnd Bergmann [this message]
2011-05-02 15:52 ` Arnd Bergmann
2011-05-02 15:52 ` Arnd Bergmann
[not found] <1518608384.2203937.1304349657551.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
2011-05-02 21:27 ` johnlinn at comcast.net
2011-05-02 21:27 ` johnlinn
2011-05-02 21:36 ` Arnd Bergmann
2011-05-02 21:36 ` Arnd Bergmann
2011-05-02 21:36 ` Arnd Bergmann
[not found] <90477150.2231869.1304372815517.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
2011-05-02 21:50 ` johnlinn at comcast.net
2011-05-02 21:50 ` johnlinn
2011-05-02 23:01 ` Russell King - ARM Linux
2011-05-02 23:01 ` Russell King - ARM Linux
2011-05-02 23:01 ` Russell King - ARM Linux
2011-05-02 23:36 ` Grant Likely
2011-05-02 23:36 ` Grant Likely
2011-05-03 7:58 ` Arnd Bergmann
2011-05-03 7:58 ` Arnd Bergmann
2011-05-03 7:58 ` Arnd Bergmann
2011-05-03 8:52 ` Russell King - ARM Linux
2011-05-03 8:52 ` Russell King - ARM Linux
2011-05-03 8:52 ` Russell King - ARM Linux
2011-05-03 10:35 ` Arnd Bergmann
2011-05-03 10:35 ` Arnd Bergmann
2011-05-03 10:35 ` Arnd Bergmann
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=201105021752.25273.arnd@arndb.de \
--to=arnd@arndb.de \
--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 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.