From: Tony Lindgren <tony@atomide.com>
To: "Stanley.Miao" <stanley.miao@windriver.com>
Cc: linux-omap@vger.kernel.org, hvaibhav@ti.com, srk@ti.com,
anuj.aggarwal@ti.com
Subject: Re: [PATCH 6/7] omap: init the gpio pinmux for mmc
Date: Tue, 11 May 2010 16:13:06 -0700 [thread overview]
Message-ID: <20100511231306.GM13931@atomide.com> (raw)
In-Reply-To: <1271745212-4474-7-git-send-email-stanley.miao@windriver.com>
* Stanley.Miao <stanley.miao@windriver.com> [100419 23:20]:
> There is two gpio for mmc use, one is for card detecting, another is
> used for checking write protect. Intialize its pinmux in case the bootloader
> doesn't set it.
>
> Signed-off-by: Stanley.Miao <stanley.miao@windriver.com>
> ---
> arch/arm/mach-omap2/devices.c | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
> index 23e4d77..df9c62a 100644
> --- a/arch/arm/mach-omap2/devices.c
> +++ b/arch/arm/mach-omap2/devices.c
> @@ -591,6 +591,13 @@ static inline void omap_hsmmc_reset(void) {}
> static inline void omap2_mmc_mux(struct omap_mmc_platform_data *mmc_controller,
> int controller_nr)
> {
> + if (mmc_controller->slots[0].switch_pin > 0)
> + omap_mux_init_gpio(mmc_controller->slots[0].switch_pin,
> + OMAP_PIN_INPUT_PULLUP);
> + if (mmc_controller->slots[0].gpio_wp > 0)
> + omap_mux_init_gpio(mmc_controller->slots[0].gpio_wp,
> + OMAP_PIN_INPUT_PULLUP);
> +
> if (cpu_is_omap2420() && controller_nr == 0) {
> omap_cfg_reg(H18_24XX_MMC_CMD);
> omap_cfg_reg(H15_24XX_MMC_CLKI);
The problem I see with this patch is that it attempts to mux
even for the GPIO pins on the companion chips, such as twl4030.
Got any ideas on how to prevent that?
Tony
next prev parent reply other threads:[~2010-05-11 23:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 6:33 [PATCH 0/7] Some am3517 related patches [V3] Stanley.Miao
2010-04-20 6:33 ` [PATCH 1/7] omap: fix the compile error if CONFIG_MTD_NAND_OMAP2 is not enabled Stanley.Miao
2010-04-22 22:59 ` [APPLIED] [PATCH 1/7] omap: fix the compile error if CONFIG_MTD_NAND_OMAP2 is Tony Lindgren
2010-04-20 6:33 ` [PATCH 2/7] omap: remove one of the define of INT_34XX_BENCH_MPU_EMUL Stanley.Miao
2010-04-22 22:59 ` [APPLIED] [PATCH 2/7] omap: remove one of the define of Tony Lindgren
2010-04-20 6:33 ` [PATCH 3/7] AM3517: rename the i2c boardinfo to make it more readable Stanley.Miao
2010-04-20 6:30 ` Felipe Balbi
2010-04-20 7:10 ` Hiremath, Vaibhav
2010-04-20 7:14 ` stanley.miao
2010-04-20 7:07 ` Hiremath, Vaibhav
2010-05-11 23:19 ` Tony Lindgren
2010-05-13 6:05 ` stanley.miao
2010-04-20 6:33 ` [PATCH 4/7] AM3517: initialize i2c subsystem after mux subsystem Stanley.Miao
2010-04-22 23:01 ` [APPLIED] " Tony Lindgren
2010-04-20 6:33 ` [PATCH 5/7] OMAP: fix a gpmc nand problem Stanley.Miao
2010-04-22 23:01 ` [APPLIED] " Tony Lindgren
2010-04-20 6:33 ` [PATCH 6/7] omap: init the gpio pinmux for mmc Stanley.Miao
2010-05-11 23:13 ` Tony Lindgren [this message]
2010-05-13 6:02 ` stanley.miao
2010-04-20 6:33 ` [PATCH 7/7] omap hsmmc: fix the hsmmc driver for am3517 Stanley.Miao
2010-05-11 23:26 ` Tony Lindgren
2010-05-13 11:53 ` stanley.miao
2010-05-13 15:58 ` Tony Lindgren
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=20100511231306.GM13931@atomide.com \
--to=tony@atomide.com \
--cc=anuj.aggarwal@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=srk@ti.com \
--cc=stanley.miao@windriver.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;
as well as URLs for NNTP newsgroup(s).