[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <510BD3B1.3040601@samsung.com>
Date: Fri, 01 Feb 2013 15:39:45 +0100
From: Marek Szyprowski <m.szyprowski@...sung.com>
To: Marek Szyprowski <m.szyprowski@...sung.com>
Cc: linux-kernel@...r.kernel.org, linux-mmc@...r.kernel.org,
Kyungmin Park <kyungmin.park@...sung.com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Liam Girdwood <lrg@...com>, Chris Ball <cjb@...top.org>,
Kevin Liu <keyuan.liu@...il.com>
Subject: Re: [PATCH 2/3] mmc: use regulator_can_change_voltage() instead of
regulator_count_voltages() hacks
Hello,
On 12/4/2012 3:01 PM, Marek Szyprowski wrote:
> mmc_regulator_set_ocr() depends on the ability of regulator to change the
> voltage value. When regulator cannot change its voltage output, some code is
> skipped to avoid reporting false errors on some boards, which use MMC hosts
> with fixed regulators (example: Samsung Goni and UniversalC210 boards).
>
> This patch replaces a hacky workaround based on regulator_count_voltages()
> value with the correct call to recently introduced
> regulator_can_change_voltage() function in regulators core.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@...sung.com>
Any chance to get this patch scheduled for v3.9?
> ---
> drivers/mmc/core/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
> index aaed768..f5a0493 100644
> --- a/drivers/mmc/core/core.c
> +++ b/drivers/mmc/core/core.c
> @@ -1137,7 +1137,7 @@ int mmc_regulator_set_ocr(struct mmc_host *mmc,
> */
> voltage = regulator_get_voltage(supply);
>
> - if (regulator_count_voltages(supply) == 1)
> + if (!regulator_can_change_voltage(supply))
> min_uV = max_uV = voltage;
>
> if (voltage < 0)
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists