The approach that's being taken by the mmc-twl4030 driver to disabling regulators is a normal and supported one so there is no need to print messages on the console warning about this - their system is functioning normally.
Signed-off-by: Mark Brown <[email protected]> --- arch/arm/mach-omap2/mmc-twl4030.c | 3 --- 1 files changed, 0 insertions(+), 3 deletions(-) diff --git a/arch/arm/mach-omap2/mmc-twl4030.c b/arch/arm/mach-omap2/mmc-twl4030.c index 8db1f29..b76a31a 100644 --- a/arch/arm/mach-omap2/mmc-twl4030.c +++ b/arch/arm/mach-omap2/mmc-twl4030.c @@ -136,14 +136,11 @@ static int twl_mmc_late_init(struct device *dev) * (which is safe for MMC, but not in general). */ if (regulator_is_enabled(hsmmc[i].vcc) > 0) { - dev_warn(dev, "APPLY REGULATOR HACK for vmmc\n"); regulator_enable(hsmmc[i].vcc); regulator_disable(hsmmc[i].vcc); } if (hsmmc[i].vcc_aux) { if (regulator_is_enabled(reg) > 0) { - dev_warn(dev, "APPLY REGULATOR HACK " - "for vmmc_aux\n"); regulator_enable(reg); regulator_disable(reg); } -- 1.6.2.1 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
