Hi, On Tue, Jun 14 2011, Sourav Poddar wrote: > From: Anand Gadiyar <gadiyar@xxxxxx> > > The OMAP HSMMC driver uses an ocr_mask to determine the > list of voltages supported by the card. It populates this > mask based on the list of voltages supported by the > regulator that supplies the voltage. > > Commit 64be97822b (omap4 hsmmc: Update ocr mask for MMC2 for > regulator to use) passed a fixed ocr_mask from the OMAP4 SDP > board file to limit the voltage to 2.9-3.0 Volts, and updated > the driver to use this mask if provided, instead of using the > regulator's supported voltages. > > However the commit is buggy - the ocr_mask is overridden > by the regulator's capabilities anyway. Fix this. > > (The bug shows up when a system-wide suspend is attempted > on the OMAP4 SDP/Blaze platforms. The eMMC card comes up > at 3V, but drops to 1.65V after the system resumes). > > Signed-off-by: Anand Gadiyar <gadiyar@xxxxxx> > Acked-by: Balaji T K <balajitk@xxxxxx> > Tested-by: Kishore Kadiyala <kishore.kadiyala@xxxxxx> > Signed-off-by: Sourav Poddar <sourav.poddar@xxxxxx> Pushed to mmc-next for 3.0-rc with Venkat's ACK, thanks. - Chris. -- Chris Ball <cjb@xxxxxxxxxx> <http://printf.net/> One Laptop Per Child -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html