From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: imx6qdl-sabresd: Add hog entry for GPIO4_10
Date: Mon, 17 Feb 2014 10:05:21 +0800 [thread overview]
Message-ID: <20140217020519.GC9879@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <1392306839-10736-1-git-send-email-fabio.estevam@freescale.com>
On Thu, Feb 13, 2014 at 01:53:58PM -0200, Fabio Estevam wrote:
> GPIO4_10 is the GPIO used to turn on the regulator that powers up the codec.
>
> Add a hog entry for it.
I'm going to be strict on hog pin use. It does not sound like a true
hog pin. Is it possible to have a pinctrl state for that regulator
setting this pin up?
Shawn
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> arch/arm/boot/dts/imx6qdl-sabresd.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> index 0d816d3..a802265 100644
> --- a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> @@ -303,6 +303,7 @@
> MX6QDL_PAD_ENET_TXD1__GPIO1_IO29 0x80000000
> MX6QDL_PAD_EIM_D22__GPIO3_IO22 0x80000000
> MX6QDL_PAD_ENET_CRS_DV__GPIO1_IO25 0x80000000
> + MX6QDL_PAD_KEY_COL2__GPIO4_IO10 0x80000000
> >;
> };
>
> --
> 1.8.1.2
>
>
next prev parent reply other threads:[~2014-02-17 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 15:53 [PATCH 1/2] ARM: dts: imx6qdl-sabresd: Add hog entry for GPIO4_10 Fabio Estevam
2014-02-13 15:53 ` [PATCH 2/2] ARM: dts: imx6qdl-sabresd: Provide min/max voltages for codec regulator Fabio Estevam
2014-02-17 2:13 ` Shawn Guo
2014-02-17 2:05 ` Shawn Guo [this message]
2014-02-17 2:11 ` [PATCH 1/2] ARM: dts: imx6qdl-sabresd: Add hog entry for GPIO4_10 Fabio Estevam
2014-02-17 2:19 ` 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=20140217020519.GC9879@S2101-09.ap.freescale.net \
--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