From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Add devicetree support for i.MX27 SoCs
Date: Wed, 29 Feb 2012 09:20:51 +0100 [thread overview]
Message-ID: <1330503654-2197-1-git-send-email-s.hauer@pengutronix.de> (raw)
Hi all,
I created the following mainly out of curiosity to find out what's
missing to support a new i.MX SoC in the devicetree. It turned out
it's not much thanks to the driver bindings which already exist for
the bigger i.MXes. So here it is.
Sascha
Sascha Hauer (3):
ARM i.MX27: Add devicetree support
ARM i.MX: Add phytec phycore-i.MX27 (aka pcm038) devicetree support
devicetree-bindings: Add documentation for i.MX generic boards
Documentation/devicetree/bindings/arm/fsl.txt | 22 +++
arch/arm/boot/dts/imx27-phytec-phycore.dts | 76 +++++++++
arch/arm/boot/dts/imx27.dtsi | 217 +++++++++++++++++++++++++
arch/arm/mach-imx/Kconfig | 8 +
arch/arm/mach-imx/Makefile | 1 +
arch/arm/mach-imx/clock-imx27.c | 18 ++
arch/arm/mach-imx/imx27-dt.c | 89 ++++++++++
arch/arm/plat-mxc/include/mach/common.h | 1 +
8 files changed, 432 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/boot/dts/imx27-phytec-phycore.dts
create mode 100644 arch/arm/boot/dts/imx27.dtsi
create mode 100644 arch/arm/mach-imx/imx27-dt.c
next reply other threads:[~2012-02-29 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 8:20 Sascha Hauer [this message]
2012-02-29 8:20 ` [PATCH 1/3] ARM i.MX27: Add devicetree support Sascha Hauer
2012-04-09 1:48 ` Chris Ball
2012-04-10 9:17 ` Sascha Hauer
2012-04-10 14:12 ` Chris Ball
2012-04-12 0:13 ` Fabio Estevam
2012-02-29 8:20 ` [PATCH 2/3] ARM i.MX: Add phytec phycore-i.MX27 (aka pcm038) " Sascha Hauer
2012-02-29 8:20 ` [PATCH 3/3] devicetree-bindings: Add documentation for i.MX generic boards Sascha Hauer
2012-03-01 7:00 ` [PATCH] Add devicetree support for i.MX27 SoCs Shawn Guo
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=1330503654-2197-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).