From: Tony Lindgren <tony@atomide.com>
To: hvaibhav@ti.com
Cc: linux-input@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/3] Mux configuration for AM3517 TouchScreen support
Date: Mon, 23 Nov 2009 09:53:26 -0800 [thread overview]
Message-ID: <20091123175326.GD22923@atomide.com> (raw)
In-Reply-To: <1258641974-2223-1-git-send-email-hvaibhav@ti.com>
* hvaibhav@ti.com <hvaibhav@ti.com> [091119 06:45]:
> From: Vaibhav Hiremath <hvaibhav@ti.com>
>
>
> Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> ---
> arch/arm/mach-omap2/mux.c | 3 +++
> arch/arm/plat-omap/include/plat/mux.h | 1 +
> 2 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/mux.c b/arch/arm/mach-omap2/mux.c
> index c18a94e..f64ce14 100644
> --- a/arch/arm/mach-omap2/mux.c
> +++ b/arch/arm/mach-omap2/mux.c
> @@ -566,6 +566,9 @@ MUX_CFG_34XX("AF9_34XX_GPIO22", 0x5ec,
> OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT_PULLUP)
> MUX_CFG_34XX("U3_34XX_GPIO61", 0x0c8,
> OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT_PULLUP)
> + /*Touch-screen*/
> + MUX_CFG_34XX("U1_34XX_GPIO65", 0x0d2,
> + OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT_PULLUP)
> };
>
> #define OMAP34XX_PINS_SZ ARRAY_SIZE(omap34xx_pins)
> diff --git a/arch/arm/plat-omap/include/plat/mux.h b/arch/arm/plat-omap/include/plat/mux.h
> index ba77de6..244afee 100644
> --- a/arch/arm/plat-omap/include/plat/mux.h
> +++ b/arch/arm/plat-omap/include/plat/mux.h
> @@ -854,6 +854,7 @@ enum omap34xx_index {
> AH14_34XX_GPIO21,
> AF9_34XX_GPIO22,
> U3_34XX_GPIO61,
> + U1_34XX_GPIO65,
> };
>
> struct omap_mux_cfg {
Let's put this on hold until we have the new mux framework
up and running. This should not stop getting in the driver
patch integrated.
Regards,
Tony
next prev parent reply other threads:[~2009-11-23 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 14:46 [PATCH 1/3] Mux configuration for AM3517 TouchScreen support hvaibhav
2009-11-23 17:53 ` Tony Lindgren [this message]
2009-11-24 14:15 ` Hiremath, Vaibhav
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=20091123175326.GD22923@atomide.com \
--to=tony@atomide.com \
--cc=hvaibhav@ti.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-omap@vger.kernel.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).