Re: [PATCH v2 16/16] mmc: host: omap_hsmmc: use "mmc_of_parse_voltage" to get ocr_avail

On 11 November 2015 at 11:26, Roger Quadros wrote: > Hi, > > On 25/08/15 17:50, Ulf Hansson wrote: >> On 3 August 2015 at 14:26, Kishon Vijay Abraham I wrote: >>> From: Roger Quadros >>> >>> For platforms that doesn't have explicit regulator control

Re: [PATCH v2 16/16] mmc: host: omap_hsmmc: use "mmc_of_parse_voltage" to get ocr_avail

Hi, On 25/08/15 17:50, Ulf Hansson wrote: > On 3 August 2015 at 14:26, Kishon Vijay Abraham I wrote: >> From: Roger Quadros >> >> For platforms that doesn't have explicit regulator control in MMC, >> populate voltage-ranges in MMC device tree node and use >>

Re: [PATCH v2 16/16] mmc: host: omap_hsmmc: use mmc_of_parse_voltage to get ocr_avail

Hi Ulf, On Tuesday 25 August 2015 08:20 PM, Ulf Hansson wrote: On 3 August 2015 at 14:26, Kishon Vijay Abraham I kis...@ti.com wrote: From: Roger Quadros rog...@ti.com For platforms that doesn't have explicit regulator control in MMC, populate voltage-ranges in MMC device tree node and use

Re: [PATCH v2 16/16] mmc: host: omap_hsmmc: use mmc_of_parse_voltage to get ocr_avail

On 3 August 2015 at 14:26, Kishon Vijay Abraham I kis...@ti.com wrote: From: Roger Quadros rog...@ti.com For platforms that doesn't have explicit regulator control in MMC, populate voltage-ranges in MMC device tree node and use mmc_of_parse_voltage to get ocr_avail I don't like this. If we

[PATCH v2 16/16] mmc: host: omap_hsmmc: use mmc_of_parse_voltage to get ocr_avail

From: Roger Quadros rog...@ti.com For platforms that doesn't have explicit regulator control in MMC, populate voltage-ranges in MMC device tree node and use mmc_of_parse_voltage to get ocr_avail Signed-off-by: Roger Quadros rog...@ti.com Signed-off-by: Lokesh Vutla lokeshvu...@ti.com