* David Brownell <david-b@xxxxxxxxxxx> [090208 11:42]: > On Tuesday 27 January 2009, Grazvydas Ignotas wrote: > > Device connected to MMC3 is assumed to be self-powered, so > > set_power() function is empty. It can't be omited because > > host driver requires it. Array size for hsmmc[] is specified > > because hsmmc[2].name is needed for MMC3 name. > > Just for the record ... this should eventually be handled > using the regulator framework, which will also help with the > decoupling of hsmmc setup from twl4030 setup. > > So for example if a given slot is hooked up to an SDIO > chip with a hard-wired 3v3 supply (Pandora MMC3, and > Overo MMC2) then it'd have a fixed voltage regulator; > and the HSMMC driver would just use that. (It would > get a "can't do that" error on disable though.) Adding to omap3-upstream and pushing to linux-omap. Tony -- 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
