From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: Scott Wood <scottwood@freescale.com>, linuxppc-dev@lists.ozlabs.org
Cc: devicetree@vger.kernel.org,
Valentin Longchamp <valentin.longchamp@keymile.com>
Subject: [PATCH v4 0/3] Support of the kmcoge4 board
Date: Tue, 22 Apr 2014 11:30:28 +0200 [thread overview]
Message-ID: <1398159031-10110-1-git-send-email-valentin.longchamp@keymile.com> (raw)
This series adds support for Keymile's COGE4 board, called kmcoge4. This
board is the reference design for further designs at Keymile around the
P2040/P2041 SoCs from Freescale. This reference design is internally
called kmp204x.
Changes in v4:
- remove the addition of the KEYMILE vendor-prefix as it is already
picked by Rob
- Take Scott's and Rob's comments regarding the bindings for the
interrupt-cells into account
- remove the partition layout for the NAND Flash as well as it was
forgotten
- Rebased on top of v3.15-rc1
Changes in v3:
- add a patch with the bindings for the KEYMILE FPGAs
- add the compatible strings for the localbus nodes
- remove the IRQ part of the board-control node as it is currently being
reworked
Changes in v2:
- add a patch so that the Zarlink vendor prefix is defined
- add some nodes on the localbus CS when possible
- only use the corenet_generic machine and add kmcoge4 to the supported
boards instead of defining a new kmp204x machine
- set better and more precise device nodes for the spi devices
- remove the partion layout for the spi_flash@0
Valentin Longchamp (3):
devicetree: bindings: add Zarlink to the vendor prefixes
devcietree: bindings: add some MFD Keymile FPGAs
powerpc/mpc85xx: add support for Keymile's kmcoge4 board
Documentation/devicetree/bindings/mfd/bfticu.txt | 25 +++
Documentation/devicetree/bindings/mfd/qriox.txt | 17 ++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/powerpc/boot/dts/kmcoge4.dts | 152 ++++++++++++++
arch/powerpc/configs/85xx/kmp204x_defconfig | 225 +++++++++++++++++++++
arch/powerpc/platforms/85xx/Kconfig | 2 +-
arch/powerpc/platforms/85xx/corenet_generic.c | 3 +-
7 files changed, 423 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/bfticu.txt
create mode 100644 Documentation/devicetree/bindings/mfd/qriox.txt
create mode 100644 arch/powerpc/boot/dts/kmcoge4.dts
create mode 100644 arch/powerpc/configs/85xx/kmp204x_defconfig
--
1.8.0.1
next reply other threads:[~2014-04-22 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 9:30 Valentin Longchamp [this message]
2014-04-22 9:30 ` [PATCH v4 1/3] devicetree: bindings: add Zarlink to the vendor prefixes Valentin Longchamp
2014-04-22 9:30 ` [PATCH v4 2/3] devcietree: bindings: add some MFD Keymile FPGAs Valentin Longchamp
2014-04-22 9:30 ` [PATCH v4 3/3] powerpc/mpc85xx: add support for Keymile's kmcoge4 board Valentin Longchamp
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=1398159031-10110-1-git-send-email-valentin.longchamp@keymile.com \
--to=valentin.longchamp@keymile.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
/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).