From: naobsd@gmail.com (FUKAUMI Naoki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] add support for Firefly-RK3288 and Rayeager PX2 boards
Date: Thu, 15 Jan 2015 11:40:56 +0900 [thread overview]
Message-ID: <1421289659-16627-1-git-send-email-naobsd@gmail.com> (raw)
This series adds support for following Rockchip SoC based boards.
- Firefly, Firefly-RK3288 (both beta and mass production version)
- ChipSPARK, Rayeager PX2
FUKAUMI Naoki (3):
dt-bindings: add vendor prefix and root compatible property for
Rockchip boards
ARM: dts: rockchip: add dts for Firefly Firefly-RK3288 boards
ARM: dts: rockchip: add dts for ChipSPARK Rayeager PX2 board
Documentation/devicetree/bindings/arm/rockchip.txt | 8 +
.../devicetree/bindings/vendor-prefixes.txt | 2 +
arch/arm/boot/dts/Makefile | 5 +-
arch/arm/boot/dts/rk3066a-rayeager.dts | 457 +++++++++++++++++++
arch/arm/boot/dts/rk3288-firefly-beta.dts | 70 +++
arch/arm/boot/dts/rk3288-firefly.dts | 70 +++
arch/arm/boot/dts/rk3288-firefly.dtsi | 498 +++++++++++++++++++++
7 files changed, 1109 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/rk3066a-rayeager.dts
create mode 100644 arch/arm/boot/dts/rk3288-firefly-beta.dts
create mode 100644 arch/arm/boot/dts/rk3288-firefly.dts
create mode 100644 arch/arm/boot/dts/rk3288-firefly.dtsi
--
2.2.2
next reply other threads:[~2015-01-15 2:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 2:40 FUKAUMI Naoki [this message]
2015-01-15 2:40 ` [PATCH 1/3] dt-bindings: add vendor prefix and root compatible property for Rockchip boards FUKAUMI Naoki
2015-01-15 14:12 ` Heiko Stübner
2015-01-15 2:40 ` [PATCH 2/3] ARM: dts: rockchip: add dts for Firefly Firefly-RK3288 boards FUKAUMI Naoki
2015-01-15 14:19 ` Heiko Stübner
2015-01-15 2:40 ` [PATCH 3/3] ARM: dts: rockchip: add dts for ChipSPARK Rayeager PX2 board FUKAUMI Naoki
2015-01-15 16:19 ` Heiko Stübner
2015-01-16 13:05 ` Naoki FUKAUMI
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=1421289659-16627-1-git-send-email-naobsd@gmail.com \
--to=naobsd@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).