On 8 June 2011 21:05, Ohad Ben-Cohen <o...@wizery.com> wrote: > 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) ?
Not really sure what you're asking. Unless its the test below? >>> 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. Which base kernel setup should I run these tests on? Thanks, Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
