From: Tony Lindgren <tony@atomide.com>
To: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH]Omap3630: Add hsmmc related checks
Date: Thu, 22 Oct 2009 10:44:08 -0700 [thread overview]
Message-ID: <20091022174408.GO16230@atomide.com> (raw)
In-Reply-To: <62121.192.168.10.89.1256233132.squirrel@dbdmail.itg.ti.com>
* Madhusudhan Chikkature <madhu.cr@ti.com> [091022 10:38]:
> From 661b13474a7af62c54f7df7a33a818c5e782cc59 Mon Sep 17 00:00:00 2001
> From: Madhu <madhu.cr@ti.com>
> Date: Wed, 21 Oct 2009 16:16:31 -0400
> Subject: [PATCH] Omap3630: Add HSMMC related checks.
>
> Add omap3630 conditional checks to devices.c to allow HSMMC3 addition and
> mux configuration for HSMMC1/2.
>
> Signed-off-by: Madhusudhan Chikkature <madhu.cr@ti.com>
> ---
> arch/arm/mach-omap2/devices.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
> index 7d4513b..1fdfc7f 100644
> --- a/arch/arm/mach-omap2/devices.c
> +++ b/arch/arm/mach-omap2/devices.c
> @@ -575,7 +575,7 @@ static inline void omap2_mmc_mux(struct
> omap_mmc_platform_data *mmc_controller,
> }
> }
>
> - if (cpu_is_omap3430()) {
> + if (cpu_is_omap3430() || cpu_is_omap3630()) {
> if (controller_nr == 0) {
> omap_cfg_reg(N28_3430_MMC1_CLK);
> omap_cfg_reg(M27_3430_MMC1_CMD);
How about using cpu_is_omap34xx() here instead? It's more future proof.
Regards,
Tony
> @@ -642,7 +642,8 @@ void __init omap2_init_mmc(struct omap_mmc_platform_data
> **mmc_data,
> irq = INT_24XX_MMC2_IRQ;
> break;
> case 2:
> - if (!cpu_is_omap44xx() && !cpu_is_omap34xx())
> + if (!cpu_is_omap44xx() && !cpu_is_omap34xx()
> + && !cpu_is_omap3630())
> return;
> base = OMAP3_MMC3_BASE;
> irq = INT_34XX_MMC3_IRQ;
> --
> 1.6.0.4
>
>
>
next prev parent reply other threads:[~2009-10-22 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 17:38 [PATCH]Omap3630: Add hsmmc related checks Madhusudhan Chikkature
2009-10-22 17:44 ` Tony Lindgren [this message]
2009-10-22 19:12 ` Madhusudhan
2009-10-22 19:36 ` Menon, Nishanth
2009-10-22 19:55 ` Madhusudhan
2009-10-23 0:08 ` Pandita, Vikram
2009-10-23 17:13 ` Madhusudhan
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=20091022174408.GO16230@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.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