From: joshc@eso.teric.us (Josh Cartwright)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: zynq: add system level control register manager
Date: Thu, 8 Nov 2012 10:01:25 -0600 [thread overview]
Message-ID: <20121108160125.GA5550@kryptos> (raw)
In-Reply-To: <20121031183610.GA2603@thinkbox>
On Wed, Oct 31, 2012 at 07:36:12PM +0100, Daniel Borkmann wrote:
> This patch for the Xilinx Zynq ARM architecture adds management of system
> level control register. The code is taken from the Xilinx-internal Linux
> Git tree and cleaned up a bit for mainline integration. Besides others,
> this patch is needed in order to integrate further drivers for Zynq such as
> the Zynq xemacps networking device driver. The patch is aganst the latest
> arm-soc tree.
>
> Signed-off-by: Daniel Borkmann <daniel.borkmann@tik.ee.ethz.ch>
> Cc: Michal Simek <michals@xilinx.com>
> Cc: John Linn <john.linn@xilinx.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> ---
Hey Daniel-
These changes will conflict with my pending clk patchset [1], as I'm
introducing bindings for the SLCR (and its clk interfaces).
It seems like a hefty chunk of the out-of-tree slcr driver is related to
configuring MIO. I think it would be really nice if this driver was
reworked to use the pinctrl subsystem, and also to provide suitable
device tree bindings.
But, at an even higher level, it would be nice to have a coordinated
plan for getting better Zynq support upstream. My implicit plan (so
far) has been:
1. Initial cleanup [get the thing booting] (done)
2. Figure out clk drivers and bindings (pending)
3. Figure out MIO pinctrl support and bindings (?)
4. Adapting out-of-tree peripheral drivers according to 2 & 3 (?)
5. Add support for SMP (?)
Step 4 has a dependency on 2 and 3, of course, the point being that we
get those into a state where we are happy with them before moving all of
the peripherals over. I believe step 5 can be done in parallel to the
others.
Arnd-
At a high level, does this sound like a suitable plan of action? Is
there something else you would like to see from those of us working on
Zynq support?
Thanks,
Josh
1: http://lists.infradead.org/pipermail/linux-arm-kernel/2012-October/129295.html
next prev parent reply other threads:[~2012-11-08 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 18:36 [PATCH] arm: zynq: add system level control register manager Daniel Borkmann
2012-11-08 16:01 ` Josh Cartwright [this message]
2012-11-09 9:49 ` Daniel Borkmann
2012-11-13 18:37 ` Josh Cartwright
2012-11-13 19:25 ` Daniel Borkmann
2012-11-14 2:29 ` Peter Crosthwaite
2012-11-12 11:35 ` Michal Simek
2012-11-13 18:33 ` Josh Cartwright
2012-11-13 18:42 ` John Linn
2012-11-13 19:03 ` Josh Cartwright
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=20121108160125.GA5550@kryptos \
--to=joshc@eso.teric.us \
--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).