From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: dove: move Dove DT to MVEBU
Date: Thu, 27 Feb 2014 22:48:30 +0100 [thread overview]
Message-ID: <530FB2AE.8020204@gmail.com> (raw)
In-Reply-To: <20140227214543.GK1872@titan.lakedaemon.net>
On 02/27/2014 10:45 PM, Jason Cooper wrote:
> On Thu, Feb 27, 2014 at 10:28:01PM +0100, Sebastian Hesselbarth wrote:
>> Thanks to DT conversion effort, Marvell Dove with DT support is now
>> ready to leave mach-dove and hop into mach-mvebu. As discussed with
>> MVEBU maintainers, we first add dove.c now and keep on migrating
>> it with Armada 3xx SoCs the next cycle.
>>
>> Patch 1 adds a DT node for the system controller found on Marvell
>> MVEBU SoCs.
>>
>> Patch 2 copies an approach taken by Andrew Lunn for Kirkwood-to-MVEBU
>> patches, that add MACH_DOVE for Dove in mach-mvebu to distinguish it
>> from ARCH_DOVE in mach-dove, where drivers still support both non-DT
>> and DT.
>>
>> Patch 3 then moves mach-dove/board-dt.c to mach-mvebu/dove.c with
>> minor cleanups and converts drivers/phy/Kconfig to MACH_DOVE for
>> a DT-only driver.
>>
>> Patch 4 finally adds MACH_DOVE and some of its drivers to multi_v7
>> defconfig.
>>
>> The patches are based on v3.14-rc4, recently posted mvebu/pinctrl-cleanup
>> and mvebu/pinctrl-dove branches: v3.14-rc4 is required for a irqchip
>> driver fix when SPARSE_IRQ is set, the pinctrl branches remove hard-coded
>> addresses from Dove's pinctrl driver.
>
> If I were to base this series on v3.14-rc1, I would need to pull in
>
> mvebu/pinctrl-dove (which draws in mvebu/pinctrl-cleanup)
> mvebu/irqchip-fixes
>
> and that should be all. iiuc, these are boot-time requirements, not
> build or merge requirements, correct?
Yes, all are boot-time requirements only.
Sebastian
prev parent reply other threads:[~2014-02-27 21:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 21:28 [PATCH 0/4] ARM: dove: move Dove DT to MVEBU Sebastian Hesselbarth
2014-02-27 21:28 ` [PATCH 1/4] ARM: dove: add system controller node Sebastian Hesselbarth
2014-03-04 4:00 ` Jason Cooper
2014-02-27 21:28 ` [PATCH 2/4] ARM: dove: prepare new Dove DT Kconfig variable Sebastian Hesselbarth
[not found] ` <20140227215145.GR1484@spo001.leaseweb.com>
2014-02-27 22:05 ` Sebastian Hesselbarth
2014-02-28 1:53 ` Mark Brown
2014-02-28 16:34 ` Jason Cooper
2014-02-28 18:12 ` Sebastian Hesselbarth
2014-03-01 8:33 ` [PATCH v2 1/5] ASoC: kirkwood: " Sebastian Hesselbarth
2014-03-01 8:33 ` [PATCH v2 2/5] watchdog: orion: " Sebastian Hesselbarth
2014-03-04 4:02 ` Jason Cooper
2014-03-01 8:33 ` [PATCH v2 3/5] thermal: dove: " Sebastian Hesselbarth
2014-03-04 4:03 ` Jason Cooper
2014-03-20 5:57 ` Zhang Rui
2014-03-01 8:33 ` [PATCH v2 4/5] mmc: " Sebastian Hesselbarth
2014-03-04 4:03 ` Jason Cooper
2014-03-27 15:24 ` Sebastian Hesselbarth
2014-04-15 18:20 ` Sebastian Hesselbarth
2014-03-01 8:33 ` [PATCH v2 5/5] phy: mvebu-sata: " Sebastian Hesselbarth
2014-03-01 13:38 ` Kishon Vijay Abraham I
2014-03-02 20:47 ` Sebastian Hesselbarth
2014-03-04 4:04 ` Jason Cooper
2014-03-04 4:01 ` [PATCH v2 1/5] ASoC: kirkwood: " Jason Cooper
2014-03-04 4:03 ` Mark Brown
2014-03-04 10:32 ` Sebastian Hesselbarth
2014-02-27 21:28 ` [PATCH 3/4] ARM: mvebu: move DT Dove to MVEBU Sebastian Hesselbarth
2014-02-27 21:40 ` Jason Cooper
2014-02-27 21:43 ` Sebastian Hesselbarth
2014-02-27 21:47 ` Jason Cooper
2014-02-27 22:03 ` [PATCH v2 " Sebastian Hesselbarth
2014-03-01 8:39 ` [PATCH v3 " Sebastian Hesselbarth
2014-03-04 4:29 ` Jason Cooper
2014-02-27 21:28 ` [PATCH 4/4] ARM: add Marvell Dove and some drivers to multi_v7 defconfig Sebastian Hesselbarth
2014-03-04 4:07 ` Jason Cooper
2014-03-17 15:29 ` Jason Cooper
2014-03-17 19:03 ` Arnd Bergmann
2014-02-27 21:45 ` [PATCH 0/4] ARM: dove: move Dove DT to MVEBU Jason Cooper
2014-02-27 21:48 ` Sebastian Hesselbarth [this message]
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=530FB2AE.8020204@gmail.com \
--to=sebastian.hesselbarth@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 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).