Hi Tony,
This patch changes the sequence of how the host drivers set_ios
function gets called during probe.
Before:
1. mmc_power_off
2. mmc_power_up
Now:
1. mmc_power_up
My guess is then; the omap driver set_ios function requires that
mmc_power_off is called before a mmc_power_up.
Hopefully
Hi,
On Tue, May 29, 2012 at 02:52:34PM +0800, Ulf Hansson wrote:
Hi Tony,
This patch changes the sequence of how the host drivers set_ios
function gets called during probe.
Before:
1. mmc_power_off
2. mmc_power_up
Now:
1. mmc_power_up
My guess is then; the omap driver set_ios
* Felipe Balbi ba...@ti.com [120529 00:46]:
Can you enable debugging on menelaus so we see what the driver is doing ?
I believe that to change the VMMC's supply voltage you need to turn off
the regulator, meaning LDO_CTRL7[1:0] = 0b00.
Looks like it's some kind of race between the slots
Hi,
On Tue, May 29, 2012 at 05:47:32AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [120529 00:46]:
Can you enable debugging on menelaus so we see what the driver is doing ?
I believe that to change the VMMC's supply voltage you need to turn off
the regulator, meaning
* Felipe Balbi ba...@ti.com [120529 05:56]:
Hi,
On Tue, May 29, 2012 at 05:47:32AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [120529 00:46]:
Can you enable debugging on menelaus so we see what the driver is doing ?
I believe that to change the VMMC's supply
Hi Ulf Chris,
Looks like commit fa550189 (mmc: core: Prevent eMMC VCC supply to be
cut from late init) causes MMC card to stop working at least with
n8x0 using drivers/mmc/host/omap.c. The card(s) on it are not eMMC.
Reverting fa550189 makes things work again. Any ideas what could
be causing
