On Tue, May 28, 2019 at 9:46 PM Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote: [snip] > > In the end, it seems like this needs a more detailed debug study, to > figure out what exactly happens during the re-initialization of the > SDIO card, rather than just papering over the problem by removing the > call to mmc_hw_reset() in the SDIO func driver. Hope this helps. To close the loop on this, we fixed this on the platform by driving a reset/enable pin during reset: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1657506 (device tree for this device is not upstream yet). The problem has to do with the fact that on re-init (without power cycle or reset/enable pin cycling), the device still sets S18A=1 in CMD5 response (that's incorrect, the device should set S18A=0 if it's already using 1.8V), so the host tries to switch voltage using CMD11, which fails, as the device is already in 1.8V mode (that's correct according to the specs). Thanks, > > Kind regards > Uffe
