* Michael Allwright <michael.allwright@xxxxxx> [150630 06:46]:
>
> Two things seem a bit strange here, 1. The power change statement to
> 0.7V, I think this should be 1.8V, right? At least this is what I see
> on the other MMC buses. 2. The set clock statement seems to repeat 4
> times before giving up and switching the power supply off.
Yes if the voltage is really 0.7V instead of 1.8V that would be
a problem for sure :)
> I instantiate the device using the device tree, here are the relevant
> sections, perhaps I have missed something?
>
> regulator_vdd18_mmc3: regulator_vdd18_mmc3 {
> compatible = "regulator-fixed";
Are you sure this is a fixed gulator? Typically you have a real
regulator somewhere controlled by a GPIO line, or on I2C like
PMIC.
> mmc3_pins: pinmux_mmc3_pins {
> pinctrl-single,pins = <
> OMAP4_IOPAD(0x114, PIN_INPUT_PULLUP | MUX_MODE3) /*
> abe_dmic_din2.gpio_121: sdmmc3_wp */
> OMAP4_IOPAD(0x116, PIN_INPUT_PULLUP | MUX_MODE3) /*
> abe_dmic_din3.gpio_122: sdmmc3_cd */
> OMAP4_IOPAD(0x118, PIN_INPUT_PULLUP | MUX_MODE1) /*
> sdmmc3_clk.gpio_123: sdmmc3_clk */
> OMAP4_IOPAD(0x11a, PIN_INPUT_PULLUP | MUX_MODE1) /*
> sdmcc3_cmd.gpio_124: sdmcc3_cmd */
> OMAP4_IOPAD(0x11c, PIN_INPUT_PULLUP | MUX_MODE1) /*
> sdmcc3_dat0.gpio_125: sdmcc3_dat0 */
> OMAP4_IOPAD(0x11e, PIN_INPUT_PULLUP | MUX_MODE1) /*
> sdmcc3_dat1.gpio_126: sdmcc3_dat1 */
> >;
> };
The pinmux configuration is often a problem too, might be worth
checking again the offsets and modes. Typically the comments
would be sdmcc3_dat1.sdmmc3_dat1 for example instead what you
have though.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
