* The voltage-ranges values from the device tree were used as-is, without first (potentially) swapping the bytes to the target CPU's endianess.
Signed-off-by: Alex Hornung <[email protected]> --- drivers/mmc/host/of_mmc_spi.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/mmc/host/of_mmc_spi.c b/drivers/mmc/host/of_mmc_spi.c index ab66f24..4bfd3e8 100644 --- a/drivers/mmc/host/of_mmc_spi.c +++ b/drivers/mmc/host/of_mmc_spi.c @@ -112,9 +112,10 @@ struct mmc_spi_platform_data *mmc_spi_get_pdata(struct spi_device *spi) for (i = 0; i < num_ranges; i++) { const int j = i * 2; u32 mask; + u32 vdd_min = be32_to_cpu(voltage_ranges[j]); + u32 vdd_max = be32_to_cpu(voltage_ranges[j + 1]); - mask = mmc_vddrange_to_ocrmask(voltage_ranges[j], - voltage_ranges[j + 1]); + mask = mmc_vddrange_to_ocrmask(vdd_min, vdd_max); if (!mask) { ret = -EINVAL; dev_err(dev, "OF: voltage-range #%d is invalid\n", i); -- 1.7.3.4 -- 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
