Re: [PATCH] ARM: OMAP: Beagle: support MMC gpio_wp differences on xM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>> -     if (system_rev >= 0x20 && system_rev <= 0x34301000) {
>> +     if (cpu_is_omap3630()) {
>> +             mmc[0].gpio_wp = -EINVAL;
>> +     } else if (system_rev >= 0x20 && system_rev <= 0x34301000) {
> [Ghorai] it's an old code. But I think we can replace the hardcode value to use omap_rev() as you are changing the same! Or default for all omap34xx?

It's actually broken too. ;)

My Bx board falls into that "Cx" if..  (and explains why the
write-protect lever on my sd card is ignored on that test system)

Looking at mainline u-boot, where system_rev is defined and passed to
the kernel, it is a constant 0x20...

I'm going to try using gpio pins 171/172/173 which were used to
identify what Beagle Hardware Rev (Ax/Bx, C2/C3, C4, xM)

>
>>               omap_mux_init_gpio(23, OMAP_PIN_INPUT);
>>               mmc[0].gpio_wp = 23;
>>       } else {

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/
--
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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux