From: Matthias Kaehlcke <matthias@kaehlcke.net>
To: Felipe Balbi <balbi@ti.com>
Cc: Matthias Kaehlcke <matthias.kaehlcke@tomtom.com>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP34xx: Add padconfig offsets for GPIOs 126-129
Date: Sun, 3 Apr 2011 13:33:28 +0200 [thread overview]
Message-ID: <20110403113328.GC1902@darwin> (raw)
In-Reply-To: <20110403110630.GB2404@legolas.emea.dhcp.ti.com>
Hi Felipe,
El Sun, Apr 03, 2011 at 02:06:31PM +0300 Felipe Balbi ha dit:
> On Fri, Apr 01, 2011 at 10:23:30PM +0200, Matthias Kaehlcke wrote:
> > Add OMAP3_CONTROL_PADCONF_GPIOxxx_OFFSET constants for GPIOs 126-129
> >
> > Signed-off-by: Matthias Kaehlcke <matthias@tomtom.com>
> > ---
> > arch/arm/mach-omap2/mux34xx.h | 4 ++++
> > 1 files changed, 4 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/arm/mach-omap2/mux34xx.h b/arch/arm/mach-omap2/mux34xx.h
> > index 6543ebf..70d2b8d 100644
> > --- a/arch/arm/mach-omap2/mux34xx.h
> > +++ b/arch/arm/mach-omap2/mux34xx.h
> > @@ -393,6 +393,10 @@
> > #define OMAP3_CONTROL_PADCONF_SAD2D_SWAKEUP_OFFSET 0xa1c
> > #define OMAP3_CONTROL_PADCONF_JTAG_RTCK_OFFSET 0xa1e
> > #define OMAP3_CONTROL_PADCONF_JTAG_TDO_OFFSET 0xa20
> > +#define OMAP3_CONTROL_PADCONF_GPIO127_OFFSET 0xa24
> > +#define OMAP3_CONTROL_PADCONF_GPIO126_OFFSET 0xa26
> > +#define OMAP3_CONTROL_PADCONF_GPIO128_OFFSET 0xa28
> > +#define OMAP3_CONTROL_PADCONF_GPIO129_OFFSET 0xa2a
>
> no users for these ?
we use these on a custom board whose board specific code won't be
mainlined. i think it still makes sense to have the constants in
mainline for the sake of completeness
kind regards
--
Matthias Kaehlcke
Embedded Linux Developer
Amsterdam
La libertad es como la mañana. Hay quienes esperan dormidos a que
llegue, pero hay quienes desvelan y caminan la noche para alcanzarla
(Subcomandante Marcos)
.''`.
using free software / Debian GNU/Linux | http://debian.org : :' :
`. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-04-03 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 20:23 [PATCH] OMAP34xx: Add padconfig offsets for GPIOs 126-129 Matthias Kaehlcke
2011-04-03 11:06 ` Felipe Balbi
2011-04-03 11:33 ` Matthias Kaehlcke [this message]
2011-04-03 18:53 ` Felipe Balbi
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=20110403113328.GC1902@darwin \
--to=matthias@kaehlcke.net \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=matthias.kaehlcke@tomtom.com \
--cc=tony@atomide.com \
/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