From: lauri.hintsala@bluegiga.com (Lauri Hintsala)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/6] ARM: apx4devkit: add pin muxing for GPIOs
Date: Tue, 10 Jul 2012 10:08:12 +0300 [thread overview]
Message-ID: <1341904092-13777-7-git-send-email-lauri.hintsala@bluegiga.com> (raw)
In-Reply-To: <1341904092-13777-1-git-send-email-lauri.hintsala@bluegiga.com>
Some pins are used as GPIOs in user space.
Signed-off-by: Lauri Hintsala <lauri.hintsala@bluegiga.com>
---
arch/arm/boot/dts/apx4devkit.dts | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/apx4devkit.dts b/arch/arm/boot/dts/apx4devkit.dts
index b30e9d7..cef8a9b 100644
--- a/arch/arm/boot/dts/apx4devkit.dts
+++ b/arch/arm/boot/dts/apx4devkit.dts
@@ -40,8 +40,13 @@
hog_pins_a: hog-gpios at 0 {
reg = <0>;
fsl,pinmux-ids = <
+ 0x0113 /* MX28_PAD_GPMI_CE1N__GPIO_0_17 */
+ 0x0153 /* MX28_PAD_GPMI_RDY1__GPIO_0_21 */
+ 0x2123 /* MX28_PAD_SSP2_MISO__GPIO_2_18 */
+ 0x2131 /* MX28_PAD_SSP2_SS0__GPIO_2_19 */
0x31c3 /* MX28_PAD_PWM3__GPIO_3_28 */
0x31e3 /* MX28_PAD_LCD_RESET__GPIO_3_30 */
+ 0x4143 /* MX28_PAD_JTAG_RTCK__GPIO_4_20 */
>;
fsl,drive-strength = <0>;
fsl,voltage = <1>;
--
1.7.9.5
next prev parent reply other threads:[~2012-07-10 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 7:08 [PATCH 0/6] Improve apx4devkit DT support Lauri Hintsala
2012-07-10 7:08 ` [PATCH 1/6] ARM: apx4devkit: add NAND support Lauri Hintsala
2012-07-10 7:08 ` [PATCH 2/6] ARM: apx4devkit: add display support Lauri Hintsala
2012-07-10 7:08 ` [PATCH 3/6] ARM: apx4devkit: fix the bus-width of SSP0 to 4 bits Lauri Hintsala
2012-07-10 7:08 ` [PATCH 4/6] ARM: apx4devkit: add SSP2 support Lauri Hintsala
2012-07-11 4:14 ` Shawn Guo
2012-07-10 7:08 ` [PATCH 5/6] ARM: apx4devkit: remove AUART3 Lauri Hintsala
2012-07-10 7:08 ` Lauri Hintsala [this message]
2012-07-11 4:16 ` [PATCH 0/6] Improve apx4devkit DT support 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=1341904092-13777-7-git-send-email-lauri.hintsala@bluegiga.com \
--to=lauri.hintsala@bluegiga.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.