From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/6] ARM: dove: Remove watchdog from DT
Date: Tue, 25 Sep 2012 11:18:26 +0200 [thread overview]
Message-ID: <20120925111826.6f4086ee@skate> (raw)
In-Reply-To: <5061754E.9050204@gmail.com>
Dear Sebastian Hesselbarth,
On Tue, 25 Sep 2012 11:11:42 +0200, Sebastian Hesselbarth wrote:
> I didn't try to post all the dove on mach-mvebu patches in the current
> release cycle, because mach-mvebu is still evolving to fast for me to keep
> up with my limited spare time. But I have dove running on mach-mvebu...
Yes, this work is really great. However, I think that instead of making
a big change at once, we should rather follow something like:
* Make mach-dove, mach-kirkwood, mach-orion5x, mach-mv78xx0 use the
new gpio/pinctrl code
* Remove the plat-orion gpio/pinctrl code
* Make mach-dove, mach-kirkwood, mach-orion5x, mach-mv78xx0 use DT for
everything.
* Remove the plat-orion common.c file (once all devices are probed
through DT, common.c is no longer needed).
* Add clock framework support for everybody, with the code in
drivers/clk/.
* Refactor the PCI code so that it can cover all cases. We should soon
be working on PCI support on Armada 370/XP, so it will show what are
the differences/issues in having something that covers all cases.
* And then, only, merge everybody in mach-mvebu.
The idea here is to make the existing
mach-{dove,kirkwood,orion5x,mv78xx0} gradually converge to DT,
pinctrl/gpio, clock and other things, and only after that merge into
mach-mvebu. It will be much easier to do the merge as most of the code
in those mach- directory will have disappeared, as well as the code in
plat-orion.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-09-25 9:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 0:02 [PATCH 0/6] Dove fixes for arm-soc/for-next Sebastian Hesselbarth
2012-09-25 0:02 ` [PATCH 1/6] ARM: dove: Add pcie clock support Sebastian Hesselbarth
2012-09-25 0:02 ` [PATCH 2/6] ARM: dove: Fix tauros2 device tree init Sebastian Hesselbarth
2012-09-25 1:22 ` Sebastian Hesselbarth
2012-09-25 5:19 ` Andrew Lunn
2012-09-25 8:56 ` Sebastian Hesselbarth
2012-09-25 0:02 ` [PATCH 3/6] ARM: dove: Fix clock names of sata and gbe Sebastian Hesselbarth
2012-09-25 0:02 ` [PATCH 4/6] ARM: dove: Restructure SoC device tree descriptor Sebastian Hesselbarth
2012-09-25 0:02 ` [PATCH 5/6] ARM: dove: Remove watchdog from DT Sebastian Hesselbarth
2012-09-25 5:35 ` Andrew Lunn
2012-09-25 9:11 ` Sebastian Hesselbarth
2012-09-25 9:18 ` Thomas Petazzoni [this message]
2012-09-25 9:46 ` Andrew Lunn
2012-09-25 10:14 ` Thomas Petazzoni
2012-09-25 10:31 ` Andrew Lunn
2012-09-25 11:20 ` Arnd Bergmann
2012-09-25 11:48 ` Arnaud Patard (Rtp)
2012-09-25 12:28 ` Arnd Bergmann
2012-10-08 18:40 ` Martin Michlmayr
2012-10-08 19:57 ` Andrew Lunn
2012-10-08 20:10 ` Arnd Bergmann
2012-10-08 20:29 ` Andrew Lunn
2012-09-25 12:33 ` Arnd Bergmann
2012-09-25 18:25 ` sebastien requiem
2012-09-25 20:02 ` Arnd Bergmann
2012-09-25 0:02 ` [PATCH 6/6] ARM: dove: Add crypto engine to DT Sebastian Hesselbarth
2012-09-25 5:37 ` [PATCH 0/6] Dove fixes for arm-soc/for-next Andrew Lunn
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=20120925111826.6f4086ee@skate \
--to=thomas.petazzoni@free-electrons.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).