From: Thomas Abraham <thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: [PATCH 0/3] Add basic device tree support for Samsung's Exynos4210 platform
Date: Fri, 15 Jul 2011 17:12:05 +0530 [thread overview]
Message-ID: <1310730128-4243-1-git-send-email-thomas.abraham@linaro.org> (raw)
This patch series adds a basic device tree based boot for Samsung's Exynos4210
platforms and specifically for smdkv310 board. Device tree based driver
probe is added for sdhci and watchdog drivers.
This patch series is based on
git.secretlab.ca/git/linux-2.6.git devicetree/test
and depends on the following patches which are not yet available in
the devicetree/test branch.
1. [PATCH] ARM: EXYNOS4: Fix card detection for sdhci 0 and 2
[http://www.mail-archive.com/linux-samsung-soc <at> vger.kernel.org/msg04704.html]
2. [PATCH] ARM: EXYNOS4: Fix missing S5P_VA_AUDSS definition
[http://www.mail-archive.com/linux-samsung-soc <at> vger.kernel.org/msg04866.html]
3. [PATCH 0/9] Add clkdev support for Samsung platforms
[http://www.mail-archive.com/linux-samsung-soc <at> vger.kernel.org/msg04874.html]
4. Consolidate the clkdev header files
[http://patchwork.ozlabs.org/patch/97862/]
Thomas Abraham (3):
mmc: sdhci-s3c: Add support for device tree based probe
arm: dts: Add nodes in smdkv310 device tree source file
arm: exynos4: Add a new Exynos4210 device tree enabled machine
Documentation/devicetree/bindings/arm/samsung.txt | 10 +-
.../devicetree/bindings/mmc/samsung-s3c-sdhci.txt | 10 ++
arch/arm/boot/dts/exynos4-smdkv310.dts | 55 ++++++++-
arch/arm/mach-exynos4/Kconfig | 10 ++
arch/arm/mach-exynos4/Makefile | 1 +
arch/arm/mach-exynos4210-dt.c | 128 ++++++++++++++++++++
drivers/mmc/host/sdhci-s3c.c | 11 ++
7 files changed, 218 insertions(+), 7 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mmc/samsung-s3c-sdhci.txt
next reply other threads:[~2011-07-15 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 11:42 Thomas Abraham [this message]
2011-07-15 11:42 ` [PATCH 1/3] mmc: sdhci-s3c: Add support for device tree based probe Thomas Abraham
2011-07-15 18:51 ` Grant Likely
2011-07-17 3:54 ` Thomas Abraham
[not found] ` <1310730128-4243-1-git-send-email-thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-07-15 11:42 ` [PATCH 2/3] arm: dts: Add nodes in smdkv310 device tree source file Thomas Abraham
[not found] ` <1310730128-4243-3-git-send-email-thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-07-15 18:57 ` Grant Likely
[not found] ` <20110715185744.GF2833-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-07-17 3:56 ` Thomas Abraham
2011-07-15 11:42 ` [PATCH 3/3] arm: exynos4: Add a new Exynos4210 device tree enabled machine Thomas Abraham
[not found] ` <1310730128-4243-4-git-send-email-thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-07-15 18:49 ` Grant Likely
[not found] ` <20110715184935.GD2833-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-07-17 4:01 ` Thomas Abraham
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=1310730128-4243-1-git-send-email-thomas.abraham@linaro.org \
--to=thomas.abraham-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.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).