Hello, We are using a OMAPL108 with 2.6.33 and noticed that the mmc clock signal stays active when idle. This doesn't seem very power efficient and we wondered if there was a reason for this. Before trying to fix this on our side I had a few questions regarding this: -Is this behavior the same in more recent versions? -Was this designed to be this way? -Would stopping the clock be a responsibility of the core (set_ios) or the host controller (between requests)?
Regards Marc -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
