From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/7] ARM: dts: imx28: move extra gpmi-nand pins into board dts
Date: Tue, 10 Jul 2012 13:36:21 +0800 [thread overview]
Message-ID: <1341898587-8462-2-git-send-email-shawn.guo@linaro.org> (raw)
In-Reply-To: <1341898587-8462-1-git-send-email-shawn.guo@linaro.org>
Only pins GPMI_CE0N and GPMI_READY0 are generally used by other boards.
Move GPMI_CE1N and GPMI_READY1 into imx28-evk.dts to make gpmi_pins_a
more general, and can be used by other boards.
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
---
arch/arm/boot/dts/imx28-evk.dts | 14 +++++++++++++-
arch/arm/boot/dts/imx28.dtsi | 2 --
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/imx28-evk.dts b/arch/arm/boot/dts/imx28-evk.dts
index 0d8739d..0444964 100644
--- a/arch/arm/boot/dts/imx28-evk.dts
+++ b/arch/arm/boot/dts/imx28-evk.dts
@@ -24,7 +24,8 @@
apbh at 80000000 {
gpmi-nand at 8000c000 {
pinctrl-names = "default";
- pinctrl-0 = <&gpmi_pins_a &gpmi_status_cfg>;
+ pinctrl-0 = <&gpmi_pins_a &gpmi_status_cfg
+ &gpmi_pins_evk>;
status = "okay";
};
@@ -64,6 +65,17 @@
fsl,voltage = <1>;
fsl,pull-up = <0>;
};
+
+ gpmi_pins_evk: gpmi-nand-evk at 0 {
+ reg = <0>;
+ fsl,pinmux-ids = <
+ 0x0110 /* MX28_PAD_GPMI_CE1N__GPMI_CE1N */
+ 0x0150 /* MX28_PAD_GPMI_RDY1__GPMI_READY1 */
+ >;
+ fsl,drive-strength = <0>;
+ fsl,voltage = <1>;
+ fsl,pull-up = <0>;
+ };
};
lcdif at 80030000 {
diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
index adb5ffc..2874adc 100644
--- a/arch/arm/boot/dts/imx28.dtsi
+++ b/arch/arm/boot/dts/imx28.dtsi
@@ -198,9 +198,7 @@
0x0060 /* MX28_PAD_GPMI_D06__GPMI_D6 */
0x0070 /* MX28_PAD_GPMI_D07__GPMI_D7 */
0x0100 /* MX28_PAD_GPMI_CE0N__GPMI_CE0N */
- 0x0110 /* MX28_PAD_GPMI_CE1N__GPMI_CE1N */
0x0140 /* MX28_PAD_GPMI_RDY0__GPMI_READY0 */
- 0x0150 /* MX28_PAD_GPMI_RDY1__GPMI_READY1 */
0x0180 /* MX28_PAD_GPMI_RDN__GPMI_RDN */
0x0190 /* MX28_PAD_GPMI_WRN__GPMI_WRN */
0x01a0 /* MX28_PAD_GPMI_ALE__GPMI_ALE */
--
1.7.5.4
next prev parent reply other threads:[~2012-07-10 5:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 5:36 [PATCH v2 0/7] Convert mxs board files to device tree Shawn Guo
2012-07-10 5:36 ` Shawn Guo [this message]
2012-07-10 5:36 ` [PATCH v2 2/7] ARM: dts: imx28: move lcdif control pins into board dts Shawn Guo
2012-07-10 5:36 ` [PATCH v2 3/7] ARM: mxs: convert m28evk board to device tree Shawn Guo
2012-07-10 7:20 ` Marek Vasut
2012-07-10 7:24 ` Shawn Guo
2012-07-10 8:32 ` Marek Vasut
2012-07-10 15:23 ` Shawn Guo
2012-07-10 15:37 ` Marek Vasut
2012-07-10 15:45 ` Shawn Guo
2012-07-10 15:51 ` Marek Vasut
2012-07-10 16:08 ` Shawn Guo
2012-07-10 16:26 ` Marek Vasut
2012-07-10 5:36 ` [PATCH v2 4/7] ARM: mxs: convert apx4devkit " Shawn Guo
2012-07-10 5:36 ` [PATCH v2 5/7] ARM: mxs: convert tx28 " Shawn Guo
2012-07-10 15:37 ` Shawn Guo
2012-07-10 5:36 ` [PATCH v2 6/7] ARM: mxs: convert stmp378x_devb " Shawn Guo
2012-07-10 5:36 ` [PATCH v2 7/7] ARM: mxs: add dtb-y target into Makefile.boot Shawn Guo
2012-07-10 5:38 ` [PATCH v2 3/7] ARM: mxs: convert m28evk board to device tree Shawn Guo
2012-07-10 5:39 ` [PATCH v2 6/7] ARM: mxs: convert stmp378x_devb " 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=1341898587-8462-2-git-send-email-shawn.guo@linaro.org \
--to=shawn.guo@linaro.org \
--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).