----- Original Message -----
From: "David Brownell" <david-b@xxxxxxxxxxx>
To: "Kumar, Purushotam" <purushotam@xxxxxx>
Cc: "Tony Lindgren" <tony@xxxxxxxxxxx>; "Purushotam Kumar" <a0876542@xxxxxxxxxxxx>; <linux-omap@xxxxxxxxxxxxxxx>; "Gole, Anant" <anantgole@xxxxxx>
Sent: Tuesday, August 05, 2008 12:40 PM
Subject: Re: [PATCH] OMAP3:devices.c: Enabling 4-bit for SD card
> On Monday 14 July 2008, Kumar, Purushotam wrote:
>> > > > if (cpu_is_omap2430() || cpu_is_omap34xx()) {
>> > > > - if (mmc->enabled)
>> > > > + if (mmc->enabled) {
>> > > > + mmc1_data.conf = *mmc;
>> > > > (void) platform_device_register(&mmc_omap_device1);
>> > > > + }
>
> I don't get it. OMAP3 uses the hsmmc code, which uses
> a "struct omap_mmc_platform_data" to configure itself.
>
> But this patch updates a "struct omap_mmc_conf" as used
> by the non-hsmmc code.
>
> So ... it's a NOP, at least for OMAP3. Right?
Hi Dave,
I think there is no difference between hsmmc code vs non-hsmmc code with respect to platform specific structure initializations.
Both of them use "omap_mmc_platform_data" as well as "omap_mmc_config" structures. I had a quick look at board-h4-mmc.c
and board-h4.c to verify this.
What this patch does is to add the missing initializtion line "mmc1_data.conf = *mmc;" for 2430 or 3430 which was present for platforms other
than these. Without this line the below condition in the hsmmc driver will not evaluate to true.
if (pdata->conf.wire4)
mmc->caps |= MMC_CAP_4_BIT_DATA;
The header "include/asm-arm/arch-omap/mmc.h" is used by both hsmmc and non-hsmmc code.
Regards,
Madhu
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
