From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 00/11] ep93xx: Move SoC private bits to core
Date: Wed, 14 Mar 2012 13:51:05 +0000 [thread overview]
Message-ID: <201203141351.06200.arnd@arndb.de> (raw)
In-Reply-To: <4F5FC8AD.4070505@gmail.com>
On Tuesday 13 March 2012, Ryan Mallon wrote:
> > There are currently eight board files (since all the dev boards got
> > merged into one file), which seems very manageable and there should be
> > no problem adding a few more over the years to come, if necessary.
>
> I doubt there will be many new boards added.
>
> > At the same time, the platform seems simple enough that you could
> > also do a device tree port in rather in a fairly short time if you
> > like, which would let you obsolete all the board files and add new
> > machines just through device tree blobs.
>
>
> Yeah, converting to device tree is one of my goals. I need to spend some
> time reading through the device tree specification first.
Ok, great!
A number of ARM9 and XScale based platforms have started the conversion
now, and there is a lot you can learn by looking at the others. I would
recommend waiting for 3.4-rc1 before you get serious with this, because
patches are pending in various trees at the moment.
There is no strict need for you to do the conversion, because you say
that the platform is basically dead and there is not much churn to be
expected in the future, but you are definitely welcome to join in.
As the first steps (after reading Documentation/devicetree/booting-without-of.txt)
the best way forward is probably to take you favourite board file and
add a DT_MACHINE_START section so you can boot the same machine
when passing an empty devicetree rather than ATAGS. Then add the interrupt
controller (should be simple for VIC), followed by gpio (needs bindings,
see Documentation/devicetree/bindings/gpio/*.txt), i2c and spi. After
you have all that infrastructure in place, you can convert every other
device, one at a time. Some (anything without platform_data) will be
trivial, others require you to come up with a new binding document
and properties to replace the platform_data. Many people try to do
the ones from board files first because it lets them remove the board
files, and only after that look at converting the core devices, but you
can do any order you like.
Arnd
next prev parent reply other threads:[~2012-03-14 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 22:48 [PATCH v4 00/11] ep93xx: Move SoC private bits to core Ryan Mallon
2012-03-13 12:35 ` Arnd Bergmann
2012-03-13 22:22 ` Ryan Mallon
2012-03-14 13:51 ` Arnd Bergmann [this message]
2012-03-14 16:20 ` H Hartley Sweeten
2012-03-14 17:00 ` Arnd Bergmann
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=201203141351.06200.arnd@arndb.de \
--to=arnd@arndb.de \
--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.