From: bengardiner@nanometrics.ca (Ben Gardiner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] ARM: davinci: introduce new board heliosv1
Date: Thu, 18 Aug 2011 17:50:46 -0400 [thread overview]
Message-ID: <cover.1313702401.git.bengardiner@nanometrics.ca> (raw)
In this series we introduce a new board type: the Nanometrics Helios hardware
platform v1. Like the other da850/omapl138 boards in arch/arm/mach-davinci
it shares lots of common data definitions. For example boot_params location
and uart config are common to this new board and to the existing da850/omapl138
boards in the tree.
To combat to potential platform-data ARM bloat that we would otherwise add
with the introduction of the new board type we propose the creation of a
da850-reference module shared among the boards. The general idea is that the
da850evm is a 'reference implementation' and as such many of the boards do
re-use this reference so they can/should share the data since builds are headed
towards multi-machine.
We first extract board setup data that is common to several of the omapl138/
da850 boards in 1,2,3,4. Then the new board type is introduced in 5.
Boot-tested this series on-top of branch master @
a0cb2d282a57fd33ae57af2f2092974c82111b77 in
git://gitorious.org/linux-davinci/linux-davinci.git on da850evm and heliosv1
hardware.
Ben Gardiner (5):
ARM: davinci: da850, omapl138: introduce shared da850 reference
components
ARM: davinci: da850, omapl138: share boot_params
ARM: davinci: da850, omapl138: share the preferred console
registration
ARM: davinci: da850, omapl138: share the davinci_uart_config
ARM: davinci: da850, omapl138: introduce new board-omapl138-heliosv1
arch/arm/mach-davinci/Kconfig | 9 ++++
arch/arm/mach-davinci/Makefile | 4 +-
arch/arm/mach-davinci/board-da850-evm.c | 18 ++-----
arch/arm/mach-davinci/board-mityomapl138.c | 16 ++-----
arch/arm/mach-davinci/board-omapl138-hawk.c | 18 ++-----
arch/arm/mach-davinci/board-omapl138-heliosv1.c | 51 ++++++++++++++++++++
arch/arm/mach-davinci/da850-reference.c | 31 ++++++++++++
.../mach-davinci/include/mach/da850-reference.h | 20 ++++++++
8 files changed, 128 insertions(+), 39 deletions(-)
create mode 100644 arch/arm/mach-davinci/board-omapl138-heliosv1.c
create mode 100644 arch/arm/mach-davinci/da850-reference.c
create mode 100644 arch/arm/mach-davinci/include/mach/da850-reference.h
--
1.7.4.1
next reply other threads:[~2011-08-18 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 21:50 Ben Gardiner [this message]
2011-08-18 21:50 ` [PATCH 1/5] ARM: davinci: da850, omapl138: introduce shared da850 reference components Ben Gardiner
2011-08-18 21:55 ` Felipe Balbi
2011-08-18 21:50 ` [PATCH 2/5] ARM: davinci: da850, omapl138: share boot_params Ben Gardiner
2011-08-18 21:56 ` Felipe Balbi
2011-08-18 21:50 ` [PATCH 3/5] ARM: davinci: da850, omapl138: share the preferred console registration Ben Gardiner
2011-08-18 21:50 ` [PATCH 4/5] ARM: davinci: da850, omapl138: share the davinci_uart_config Ben Gardiner
2011-08-18 21:57 ` Felipe Balbi
2011-08-18 21:50 ` [PATCH 5/5] ARM: davinci: da850, omapl138: introduce new board-omapl138-heliosv1 Ben Gardiner
2011-08-18 22:02 ` Felipe Balbi
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=cover.1313702401.git.bengardiner@nanometrics.ca \
--to=bengardiner@nanometrics.ca \
--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).