On Wed, Jun 8, 2011 at 5:21 PM, Daniel Drake <dsd@xxxxxxxxxx> wrote: >> 1. How come power off+on works for you in the first time, but doesn't >> work in the second time ? > > I assume it is because a different codepath was taken in order to > power up the device the first time, before it then got powered down, > compared to the codepath that failed to power it up the 2nd time. My > efforts so far have been based around eliminating the differences in > those codepaths, and this approach seems to be successful. We have 3 power-on paths here: on boot, on insmod, and and resume. I understand the first one succeeds (naturally), and the last one failed, but now I'm confused what was the outcome of the 2nd (without sending a reset cmd) ? >> 3. what if you do a series of insmod+rmmod ? does this work ? (power >> should be taken down and up every time) > > rmmod doesn't appear to take down the power. Let's nail this one first. if we get it right, the rest will immediately follow. Please reboot, and immediately after booting (without insmoding the driver) tell me what's the output of : mount -t debugfs none /sys/kernel/debug cat /sys/kernel/debug/mmc1/ios Then insmod the driver, and tell me again what's the output of /sys/.../mmc1/ios. Please send a contiguous terminal session of these steps (incl. the boot messages), thanks ! -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
