From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Add dts info for wandboard GPIO lines.
Date: Tue, 30 Jun 2015 10:08:38 +0200 [thread overview]
Message-ID: <20150630080838.GA18829@pengutronix.de> (raw)
In-Reply-To: <1375306847-14340-2-git-send-email-panetta.mike@gmail.com>
Hello,
while starting to use the GPIO lines being available on the JP4
connector of the wand board I stumbled over this patch on the linux arm
kernel mailing list:
On Wed, Jul 31, 2013 at 05:40:47PM -0400, Michael Panetta wrote:
> diff --git a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi b/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
> index a55113e..b40bbe1 100644
> --- a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
> @@ -84,6 +84,23 @@
> >;
> };
> };
> +
> + gpio {
> + pinctrl_gpio: gpiogrp {
> + fsl,pins = <
> + MX6QDL_PAD_EIM_DA12__GPIO3_IO12 0x80000000 /* GPIO3_12 EDM pin 255 */
Looking at the "Wandboard User Guide, Revision B1"[1] I'd say EDM pin
255 on the board drives the signal GPIO3_11 and so TP128 on the board.
Instead it's pad MX6QDL_PAD_EIM_DA11 (and so GPIO3_IO11) that is
connected to EDM pin 256 which is called GPIO3_12 for the Wandboard.
Unless I'm failing to read the schematics, this is an unfortunate naming
mismatch that someone might want to fix?!
Best regards
Uwe
PS: The patch was never applied to the mainline kernel.
[1] http://www.wandboard.org/images/downloads/wbquad-revb1-userguide.pdf
> + MX6QDL_PAD_EIM_DA11__GPIO3_IO11 0x80000000 /* GPIO3_11 EDM pin 256 */
> + MX6QDL_PAD_EIM_DA10__GPIO3_IO10 0x80000000 /* GPIO3_10 EDM pin 257 */
> + MX6QDL_PAD_EIM_D27__GPIO3_IO27 0x80000000 /* GPIO3_27 EDM pin 258 */
> + MX6QDL_PAD_EIM_D26__GPIO3_IO26 0x80000000 /* GPIO3_26 EDM pin 259 */
> + MX6QDL_PAD_EIM_BCLK__GPIO6_IO31 0x80000000 /* GPIO6_31 EDM pin 260 */
> + MX6QDL_PAD_EIM_DA8__GPIO3_IO08 0x80000000 /* GPIO3_8 EDM pin 261 */
> + MX6QDL_PAD_ENET_RX_ER__GPIO1_IO24 0x80000000 /* GPIO1_24 EDM pin 262 */
> + MX6QDL_PAD_GPIO_19__GPIO4_IO05 0x80000000 /* GPIO4_5 EDM pin 263 */
> + MX6QDL_PAD_SD3_RST__GPIO7_IO08 0x80000000 /* GPIO7_8 EDM pin 264 */
> + >;
> + };
> + };
> };
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2015-06-30 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 21:40 [PATCH] ARM: dts: imx6qdl-wandboard: add gpio lines to wandboard shared dtsi Michael Panetta
2013-07-31 21:40 ` [PATCH] Add dts info for wandboard GPIO lines Michael Panetta
2015-06-30 8:08 ` Uwe Kleine-König [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-06 21:35 [Repost PATCH] ARM: dts: imx6qdl-wandboard: add gpio lines to wandboard shared dtsi Michael Panetta
2013-08-06 21:35 ` [PATCH] Add dts info for wandboard GPIO lines Michael Panetta
2013-08-06 21:39 ` Fabio Estevam
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=20150630080838.GA18829@pengutronix.de \
--to=u.kleine-koenig@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 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.