From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] Xilinx Zynq changes for v3.15
Date: Tue, 11 Mar 2014 14:33:31 -0700 [thread overview]
Message-ID: <20140311213331.GA6429@quad.lixom.net> (raw)
In-Reply-To: <531D746A.4020903@monstr.eu>
On Mon, Mar 10, 2014 at 09:14:34AM +0100, Michal Simek wrote:
> Hi,
>
> please pull these changes to your arm-soc tree. This branch is based
> on zynq/dt branch from the second pull request.
> I have kept OCM patch in this branch because it depends on slcr changes
> done here. If you want to send another pull request just for this OCM
> patch based on this branch, please let me know.
>
> Changes in v2: Fix incorrect git repo url
Thanks!
> The following changes since commit 3795e91d2abb25164dda5687ca680a7ab940c447:
>
> arm: dt: zynq: Add fclk-enable property to clkc node (2014-02-03 17:00:24 +0100)
>
> are available in the git repository at:
>
> git://git.xilinx.com/linux-xlnx.git tags/zynq-cleanup-for-3.15
>
> for you to fetch changes up to e9aa3e3a5bb2d64515648537100e5cf9b863e01a:
>
> ARM: zynq: Add support for SOC_BUS (2014-02-20 16:08:47 +0100)
>
> ----------------------------------------------------------------
> arm: Xilinx Zynq cleanup patches for v3.15
>
> - Redesign SLCR initialization to enable
> driver developing which targets SLCR space
> - Add OCM driver
> - Add SOC_BUS support
>
> ----------------------------------------------------------------
> Michal Simek (8):
> ARM: zynq: Split slcr in two parts
> ARM: zynq: Map I/O memory on clkc init
> ARM: zynq: Add and use zynq_slcr_read/write() helper functions
> ARM: zynq: Introduce zynq_slcr_unlock()
> ARM: zynq: Add OCM driver
Looking at the patches in the branch, this is the one I have most concern with.
I think it will require more work to get it in shape to get merged, as per
those comments.
I think it's worth to merge the other stuff though, so can you rebuild the
branch without the OCM driver so we can get the rest in for 3.15 even if the
OCM piece ends up taking longer?
-Olof
next prev parent reply other threads:[~2014-03-11 21:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 15:26 [GIT PULL] Xilinx Zynq changes for v3.15 Michal Simek
2014-02-28 7:18 ` Michal Simek
2014-03-09 6:07 ` Olof Johansson
2014-03-10 8:15 ` Michal Simek
2014-03-10 8:14 ` [GIT PULL v2] " Michal Simek
2014-03-11 21:33 ` Olof Johansson [this message]
2014-03-12 12:03 ` Michal Simek
2014-03-17 4:44 ` Olof Johansson
2014-03-17 15:20 ` [GIT PULL v3] " Michal Simek
2014-03-24 6:50 ` Michal Simek
2014-03-25 6:03 ` Olof Johansson
2014-03-27 1:28 ` Arnd Bergmann
2014-03-27 11:41 ` Michal Simek
2014-04-25 8:52 ` Michal Simek
2014-04-25 9:00 ` Arnd Bergmann
2014-04-25 9:49 ` Michal Simek
2014-04-25 11:16 ` Arnd Bergmann
2014-04-25 11:31 ` Michal Simek
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=20140311213331.GA6429@quad.lixom.net \
--to=olof@lixom.net \
--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.