The last dependency of that code on twl4030 specific behavior was coupled to regulator usage ... and, hey, there's a regulator framework to hide such details! The first four of these patches are from the regulator-next tree: - regulator: enumerate voltages - regulator: twl4030 voltage enumeration - regulator: twl4030 voltage enumeration cleanups - MMC: regulator utilities More precisely ... the first three are, but the wrong version of the fourth got merged; that should get sorted out soonish. The last patch does the magic: - mmc-twl4030 uses regulator framework This works if the boards have hooked up their regulators to the MMC devices. Beagle does that; so does the 3430 SDP (which has a second 1.8V SD/MMCplus slot). I'll resend a patch doing that for Overo. So for example two of Adrian's patches from yesterday are now subsumed by the regulator framework. To have MMC2 hook up to an eMMC chip that needs VccQ for interface level shifting, just hook up the "aux" supply to that MMC device. To have it use the VAUX3 supply instead of VMMC2, just be sure to hook up the right regulator. -- 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
