From: Tony Lindgren <tony@atomide.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"Jadav, Brijesh R" <brijesh.j@ti.com>,
"Shah, Hardik" <hardik.shah@ti.com>
Subject: Re: [PATCH 1/2] Pad configuration for OMAP3EVM Multi-Media Daughter Card Support
Date: Fri, 20 Feb 2009 11:37:45 -0800 [thread overview]
Message-ID: <20090220193744.GY7414@atomide.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739403FA81B81F@dbde02.ent.ti.com>
* Hiremath, Vaibhav <hvaibhav@ti.com> [090210 04:11]:
>
>
> Thanks,
> Vaibhav Hiremath
>
> > -----Original Message-----
> > From: Hiremath, Vaibhav
> > Sent: Friday, January 30, 2009 12:52 AM
> > To: linux-omap@vger.kernel.org
> > Cc: linux-media@vger.kernel.org; Hiremath, Vaibhav; Jadav, Brijesh
> > R; Shah, Hardik
> > Subject: [PATCH 1/2] Pad configuration for OMAP3EVM Multi-Media
> > Daughter Card Support
> >
> > From: Vaibhav Hiremath <hvaibhav@ti.com>
> >
> > On OMAP3EVM Mass Market Daugher Card following GPIO pins are being
> > used -
> >
> > GPIO134 --> Enable/Disable TVP5146 interface
> > GPIO54 --> Enable/Disable Expansion Camera interface
> > GPIO136 --> Enable/Disable Camera (Sensor) interface
> >
> > Added entry for the above GPIO's in mux.c and mux.h file
> >
> > Signed-off-by: Brijesh Jadav <brijesh.j@ti.com>
> > Signed-off-by: Hardik Shah <hardik.shah@ti.com>
> > Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> > ---
> > arch/arm/mach-omap2/mux.c | 6 ++++++
> > arch/arm/plat-omap/include/mach/mux.h | 5 ++++-
> > 2 files changed, 10 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/arm/mach-omap2/mux.c b/arch/arm/mach-omap2/mux.c
> > index 1556688..d226d81 100644
> > --- a/arch/arm/mach-omap2/mux.c
> > +++ b/arch/arm/mach-omap2/mux.c
> > @@ -471,6 +471,12 @@ MUX_CFG_34XX("AF5_34XX_GPIO142", 0x170,
> > OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_OUTPUT)
> > MUX_CFG_34XX("AE5_34XX_GPIO143", 0x172,
> > OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_OUTPUT)
> > +MUX_CFG_34XX("AG4_34XX_GPIO134", 0x160,
> > + OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_OUTPUT)
> > +MUX_CFG_34XX("U8_34XX_GPIO54", 0x0b4,
> > + OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_OUTPUT)
> > +MUX_CFG_34XX("AE4_34XX_GPIO136", 0x164,
> > + OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_OUTPUT)
> >
> > };
> >
> > diff --git a/arch/arm/plat-omap/include/mach/mux.h b/arch/arm/plat-
> > omap/include/mach/mux.h
> > index 67fddec..ace037f 100644
> > --- a/arch/arm/plat-omap/include/mach/mux.h
> > +++ b/arch/arm/plat-omap/include/mach/mux.h
> > @@ -795,7 +795,10 @@ enum omap34xx_index {
> > AF6_34XX_GPIO140_UP,
> > AE6_34XX_GPIO141,
> > AF5_34XX_GPIO142,
> > - AE5_34XX_GPIO143
> > + AE5_34XX_GPIO143,
> > + AG4_34XX_GPIO134,
> > + U8_34XX_GPIO54,
> > + AE4_34XX_GPIO136,
> > };
> >
> [Hiremath, Vaibhav] If there are no review comments on this then probably this patch should go through, since this is independent and being used with Multi-Media Daughter card support.
Added to omap-upstream queue and pushing to linux-omap.
Tony
prev parent reply other threads:[~2009-02-20 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 19:22 [PATCH 1/2] Pad configuration for OMAP3EVM Multi-Media Daughter Card Support hvaibhav
2009-02-10 12:11 ` Hiremath, Vaibhav
2009-02-20 19:37 ` Tony Lindgren [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=20090220193744.GY7414@atomide.com \
--to=tony@atomide.com \
--cc=brijesh.j@ti.com \
--cc=hardik.shah@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-media@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