From: Thomas Abraham <thomas.abraham@linaro.org>
To: devicetree-discuss@lists.ozlabs.org, linux-samsung-soc@vger.kernel.org
Cc: grant.likely@secretlab.ca, rob.herring@calxeda.com,
arnd@arndb.de, kgene.kim@samsung.com,
linux-arm-kernel@lists.infradead.org, patches@linaro.org
Subject: [PATCH 0/2] ARM: Samsung: Add basic device tree support for Exynos4 boards
Date: Tue, 11 Oct 2011 19:43:14 +0530 [thread overview]
Message-ID: <1318342396-26178-1-git-send-email-thomas.abraham@linaro.org> (raw)
This patchset adds a new basic device tree enabled machine/board file which is
based on the Samsung's Exynos4 family of SoC's. Also included in this patchset is the
dts file for Exynos4210 SoC, Samsung's SMDKV310 board and Insignal's Origen board.
The Exynos4210 dts file includes support for IRQ, GPIO, WDT, RTC, UART, SDHCI, Keypad,
DMA and I2C controllers. As device tree coverage for Exynos4210 increases, additional
device nodes to represent the controllers should be added.
The device tree enabled machine file enables boot on two boards based on the
Exynos4210 SoC. This provides a starting point to add additional device tree support
on these boards, migrate other existing Exynos4 based boards to use device tree
and enable device tree based boot on new upcoming boards.
This patchset has been tested on the following tree:
https://github.com/kgene/linux-samsung.git branch: for-next
Thomas Abraham (2):
ARM: Samsung: Add Exynos4 device tree enabled board file
ARM: dts: Add intial dts file for Exynos4210 SoC, SMDKV310 and Origen board
.../devicetree/bindings/arm/insignal-boards.txt | 8 +
.../devicetree/bindings/arm/samsung-boards.txt | 8 +
arch/arm/boot/dts/exynos4210-origen.dts | 137 +++++++
arch/arm/boot/dts/exynos4210-smdkv310.dts | 182 +++++++++
arch/arm/boot/dts/exynos4210.dtsi | 403 ++++++++++++++++++++
arch/arm/mach-exynos4/Kconfig | 14 +
arch/arm/mach-exynos4/Makefile | 2 +
arch/arm/mach-exynos4/mach-exynos4-dt.c | 85 ++++
8 files changed, 839 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/insignal-boards.txt
create mode 100644 Documentation/devicetree/bindings/arm/samsung-boards.txt
create mode 100644 arch/arm/boot/dts/exynos4210-origen.dts
create mode 100644 arch/arm/boot/dts/exynos4210-smdkv310.dts
create mode 100644 arch/arm/boot/dts/exynos4210.dtsi
create mode 100644 arch/arm/mach-exynos4/mach-exynos4-dt.c
next reply other threads:[~2011-10-11 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 14:13 Thomas Abraham [this message]
2011-10-11 14:13 ` [PATCH 1/2] ARM: Samsung: Add Exynos4 device tree enabled board file Thomas Abraham
2011-10-13 17:51 ` Grant Likely
2011-10-14 11:28 ` Kukjin Kim
[not found] ` <000201cc8a64$6775ae30$36610a90$%kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2011-10-14 12:22 ` Rob Herring
2011-10-11 14:13 ` [PATCH 2/2] ARM: dts: Add intial dts file for Exynos4210 SoC, SMDKV310 and Origen board Thomas Abraham
2011-10-13 17:52 ` Grant Likely
2011-10-14 11:29 ` Kukjin Kim
2011-10-24 13:02 ` [PATCH 0/2] ARM: Samsung: Add basic device tree support for Exynos4 boards Kukjin Kim
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=1318342396-26178-1-git-send-email-thomas.abraham@linaro.org \
--to=thomas.abraham@linaro.org \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rob.herring@calxeda.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).