From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] zynq subarch cleanups
Date: Tue, 23 Oct 2012 15:50:48 -0500 [thread overview]
Message-ID: <50870328.7080800@gmail.com> (raw)
In-Reply-To: <201210231441.29107.arnd@arndb.de>
On 10/23/2012 09:41 AM, Arnd Bergmann wrote:
> On Monday 22 October 2012, Josh Cartwright wrote:
>> Hey all-
>>
>> Things have been relatively quiet on the Zynq front lately. This
>> patchset does a bit of cleanup of the Zynq subarchitecture. It was the
>> necessary set of things I had to do to get a zynq target booting with
>> the upstream qemu model. It removes some unused clock infrastructure,
>> adds DT support for the GIC, and moves around peripheral mappings.
>
> Ok, thanks for these patches. As we have moved on for some of these issues,
> I'll comment on how to go even further. On a global scale, I wonder
> if there are any obstacles for enabling CONFIG_MULTIPLATFORM on Zynq
> as we have done for most of the other recently added platform.
IIRC, the only thing I saw preventing it was the custom clk usage.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robherring2@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Cartwright <josh.cartwright@ni.com>,
arm@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
John Linn <john.linn@xilinx.com>
Subject: Re: [PATCH v2 0/4] zynq subarch cleanups
Date: Tue, 23 Oct 2012 15:50:48 -0500 [thread overview]
Message-ID: <50870328.7080800@gmail.com> (raw)
In-Reply-To: <201210231441.29107.arnd@arndb.de>
On 10/23/2012 09:41 AM, Arnd Bergmann wrote:
> On Monday 22 October 2012, Josh Cartwright wrote:
>> Hey all-
>>
>> Things have been relatively quiet on the Zynq front lately. This
>> patchset does a bit of cleanup of the Zynq subarchitecture. It was the
>> necessary set of things I had to do to get a zynq target booting with
>> the upstream qemu model. It removes some unused clock infrastructure,
>> adds DT support for the GIC, and moves around peripheral mappings.
>
> Ok, thanks for these patches. As we have moved on for some of these issues,
> I'll comment on how to go even further. On a global scale, I wonder
> if there are any obstacles for enabling CONFIG_MULTIPLATFORM on Zynq
> as we have done for most of the other recently added platform.
IIRC, the only thing I saw preventing it was the custom clk usage.
Rob
next prev parent reply other threads:[~2012-10-23 20:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 21:10 [PATCH v2 0/4] zynq subarch cleanups Josh Cartwright
2012-10-22 21:10 ` Josh Cartwright
2012-10-22 21:11 ` [PATCH v2 1/4] ARM: annotate VMALLOC_END definition with _AC Josh Cartwright
2012-10-22 21:11 ` Josh Cartwright
2012-10-22 21:12 ` [PATCH v2 2/4] zynq: move static peripheral mappings Josh Cartwright
2012-10-22 21:12 ` Josh Cartwright
2012-10-23 14:50 ` Arnd Bergmann
2012-10-23 14:50 ` Arnd Bergmann
2012-10-23 16:26 ` Josh Cartwright
2012-10-23 16:26 ` Josh Cartwright
2012-10-23 17:48 ` Arnd Bergmann
2012-10-23 17:48 ` Arnd Bergmann
2012-10-23 20:27 ` Nick Bowler
2012-10-23 20:27 ` Nick Bowler
2012-10-23 23:42 ` Josh Cartwright
2012-10-23 23:42 ` Josh Cartwright
2012-10-24 20:19 ` Nick Bowler
2012-10-24 20:19 ` Nick Bowler
2012-10-23 20:09 ` Rob Herring
2012-10-23 20:09 ` Rob Herring
2012-10-23 20:53 ` Josh Cartwright
2012-10-23 20:53 ` Josh Cartwright
2012-10-23 21:17 ` Nick Bowler
2012-10-23 21:17 ` Nick Bowler
2012-10-23 21:24 ` Josh Cartwright
2012-10-23 21:24 ` Josh Cartwright
2012-10-22 21:12 ` [PATCH v2 3/4] zynq: use GIC device tree bindings Josh Cartwright
2012-10-22 21:12 ` Josh Cartwright
2012-10-22 21:13 ` [PATCH v2 4/4] zynq: remove use of CLKDEV_LOOKUP Josh Cartwright
2012-10-22 21:13 ` Josh Cartwright
2012-10-23 14:41 ` [PATCH v2 0/4] zynq subarch cleanups Arnd Bergmann
2012-10-23 14:41 ` Arnd Bergmann
2012-10-23 20:50 ` Rob Herring [this message]
2012-10-23 20:50 ` Rob Herring
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=50870328.7080800@gmail.com \
--to=robherring2@gmail.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 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.