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 23:36:52 +0200 [thread overview]
Message-ID: <201105022336.52663.arnd@arndb.de> (raw)
In-Reply-To: <538266033.2230575.1304371624720.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
On Monday 02 May 2011 23:27:04 johnlinn at comcast.net wrote:
> Yes we could explain hard coded numbers. Ideally GIC driver would support
> device tree it seems like to me.
>
> Seems like the GIC driver could remap it's own memory but maybe that won't
> work across all platforms and then the platform would need to do it.
Why not just add a stub in the xilinx platform for now that remaps the
memory using ioremap and calls the regular GIC initialization?
That function can then easily be moved to common code when another
platform uses it.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: johnlinn@comcast.net, nicolas.pitre@linaro.org,
linux@arm.linux.org.uk, devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, grant.likely@secretlab.ca,
john.linn@xilinx.com
Subject: Re: [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support
Date: Mon, 2 May 2011 23:36:52 +0200 [thread overview]
Message-ID: <201105022336.52663.arnd@arndb.de> (raw)
In-Reply-To: <538266033.2230575.1304371624720.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
On Monday 02 May 2011 23:27:04 johnlinn@comcast.net wrote:
> Yes we could explain hard coded numbers. Ideally GIC driver would support
> device tree it seems like to me.
>
> Seems like the GIC driver could remap it's own memory but maybe that won't
> work across all platforms and then the platform would need to do it.
Why not just add a stub in the xilinx platform for now that remaps the
memory using ioremap and calls the regular GIC initialization?
That function can then easily be moved to common code when another
platform uses it.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: nicolas.pitre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
johnlinn-Wuw85uim5zDR7s880joybQ@public.gmane.org
Subject: Re: [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support
Date: Mon, 2 May 2011 23:36:52 +0200 [thread overview]
Message-ID: <201105022336.52663.arnd@arndb.de> (raw)
In-Reply-To: <538266033.2230575.1304371624720.JavaMail.root-2//McUVsTWSpNjDeV5bKuMcQQQXLS/gekU1+q43GAIqQvBXZIOnqxg@public.gmane.org>
On Monday 02 May 2011 23:27:04 johnlinn-Wuw85uim5zDR7s880joybQ@public.gmane.org wrote:
> Yes we could explain hard coded numbers. Ideally GIC driver would support
> device tree it seems like to me.
>
> Seems like the GIC driver could remap it's own memory but maybe that won't
> work across all platforms and then the platform would need to do it.
Why not just add a stub in the xilinx platform for now that remaps the
memory using ioremap and calls the regular GIC initialization?
That function can then easily be moved to common code when another
platform uses it.
Arnd
next prev parent reply other threads:[~2011-05-02 21:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1518608384.2203937.1304349657551.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
2011-05-02 21:27 ` [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support johnlinn at comcast.net
2011-05-02 21:27 ` johnlinn
2011-05-02 21:36 ` Arnd Bergmann [this message]
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
2011-05-02 5:07 [RFC PATCH 0/4] ARM: Basic Xilinx Support 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
2011-05-02 15:52 ` Arnd Bergmann
2011-05-02 15:52 ` 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=201105022336.52663.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.