From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx6qdl-wandboard: Move FEC reset pin into the FEC pin group
Date: Tue, 29 Apr 2014 13:24:56 +0800 [thread overview]
Message-ID: <20140429052454.GC16451@dragon> (raw)
In-Reply-To: <1398284002-14396-1-git-send-email-festevam@gmail.com>
On Wed, Apr 23, 2014 at 05:13:22PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Remove GPIO3_29 (FEC PHY reset pin) from the hog group and place it into
> pinctrl_enet pin group instead.
If you can clean up the pinctrl settings to kill hog group completely
for the board, I would be happy to take the patch. Otherwise, let's
leave it there for now, until you see a real problem with having the
pin in hog group than pinctrl_enet.
Shawn
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> arch/arm/boot/dts/imx6qdl-wandboard.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi b/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
> index 5c6f10c..79498ca 100644
> --- a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
> @@ -104,7 +104,6 @@
> MX6QDL_PAD_ENET_RXD1__GPIO1_IO26 0x80000000 /* WL_REG_ON */
> MX6QDL_PAD_ENET_TXD1__GPIO1_IO29 0x80000000 /* WL_HOST_WAKE */
> MX6QDL_PAD_ENET_TXD0__GPIO1_IO30 0x80000000 /* WL_WAKE */
> - MX6QDL_PAD_EIM_D29__GPIO3_IO29 0x80000000
> >;
> };
>
> @@ -136,6 +135,7 @@
> MX6QDL_PAD_RGMII_RX_CTL__RGMII_RX_CTL 0x1b0b0
> MX6QDL_PAD_GPIO_16__ENET_REF_CLK 0x4001b0a8
> MX6QDL_PAD_GPIO_6__ENET_IRQ 0x000b1
> + MX6QDL_PAD_EIM_D29__GPIO3_IO29 0x80000000
> >;
> };
>
> --
> 1.8.3.2
>
>
>
prev parent reply other threads:[~2014-04-29 5:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 20:13 [PATCH] ARM: dts: imx6qdl-wandboard: Move FEC reset pin into the FEC pin group Fabio Estevam
2014-04-29 5:24 ` Shawn Guo [this message]
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=20140429052454.GC16451@dragon \
--to=shawn.guo@freescale.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 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).