From: Tony Lindgren <tony@atomide.com>
To: kmpark@infradead.org
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] OMAP: Define more OMAP24XX GPIOs pinout
Date: Wed, 11 Jul 2007 03:52:22 -0700 [thread overview]
Message-ID: <20070711105217.GB19166@atomide.com> (raw)
In-Reply-To: <002c01c7bc7b$6ccd1f50$e1ac580a@swcenter.sec.samsung.co.kr>
* Kyungmin Park <kyungmin.park@samsung.com> [070702 00:36]:
> [PATCH] OMAP: Define more OMAP24XX GPIOs pinout
>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> --
> diff --git a/arch/arm/mach-omap2/mux.c b/arch/arm/mach-omap2/mux.c
> index 4c82860..37e364d 100644
> --- a/arch/arm/mach-omap2/mux.c
> +++ b/arch/arm/mach-omap2/mux.c
> @@ -78,6 +78,10 @@ MUX_CFG_24XX("AA8_242X_GPIO58", 0x0ea, 3,
> 0, 0, 1)
> MUX_CFG_24XX("Y20_24XX_GPIO60", 0x12c, 3, 0, 0,
> 1)
> MUX_CFG_24XX("W4__24XX_GPIO74", 0x0f2, 3, 0, 0,
> 1)
> MUX_CFG_24XX("M15_24XX_GPIO92", 0x10a, 3, 0, 0,
> 1)
> +MUX_CFG_24XX("P20_24XX_GPIO93", 0x10b, 3, 0, 0,
> 1)
> +MUX_CFG_24XX("P18_24XX_GPIO95", 0x10d, 3, 0, 0,
> 1)
> +MUX_CFG_24XX("M18_24XX_GPIO96", 0x10e, 3, 0, 0,
> 1)
> +MUX_CFG_24XX("L14_24XX_GPIO97", 0x10f, 3, 0, 0,
> 1)
> MUX_CFG_24XX("J15_24XX_GPIO99", 0x113, 3, 1, 1,
> 1)
> MUX_CFG_24XX("V14_24XX_GPIO117", 0x128, 3, 1, 0, 1)
> MUX_CFG_24XX("P14_24XX_GPIO125", 0x140, 3, 1, 1, 1)
> diff --git a/include/asm-arm/arch-omap/mux.h b/include/asm-arm/arch-omap/mux.h
> index 90e454e..fc682b5 100644
> --- a/include/asm-arm/arch-omap/mux.h
> +++ b/include/asm-arm/arch-omap/mux.h
> @@ -470,6 +470,10 @@ enum omap24xx_index {
> Y20_24XX_GPIO60,
> W4__24XX_GPIO74,
> M15_24XX_GPIO92,
> + P20_24XX_GPIO93,
> + P18_24XX_GPIO95,
> + M18_24XX_GPIO96,
> + L14_24XX_GPIO97,
> J15_24XX_GPIO99,
> V14_24XX_GPIO117,
> P14_24XX_GPIO125,
Pushing after manual merging because of wrapping.
Tony
prev parent reply other threads:[~2007-07-11 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 7:34 [PATCH] OMAP: Define more OMAP24XX GPIOs pinout Kyungmin Park
2007-07-11 10:52 ` 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=20070711105217.GB19166@atomide.com \
--to=tony@atomide.com \
--cc=kmpark@infradead.org \
--cc=linux-omap-open-source@linux.omap.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.