On 2016-10-18, Paul Kocialkowski wrote: > Le mardi 18 octobre 2016 ? 11:21 +0200, Heiko St?bner a ?crit?: >> Am Sonntag, 16. Oktober 2016, 21:49:43 schrieb Paul Kocialkowski: >> > Le mardi 27 septembre 2016 ? 13:53 -0700, Vagrant Cascadian a ?crit : >> > > >> > > This essentially mimics what was done with rk3288-veyron-minnie in >> > > commit 984926781122f034d5bc9962815d135b6c4a8e1d. >> > > >> > > The eMMC of the speedy Chromebook also appears to need the same tuning >> > > workaround, as it frequently fails to recognize the eMMC without it. >> > >> > I have a device where (without this patch) eMMC sometimes fails, with: >> > [????3.561010] dwmmc_rockchip ff0f0000.dwmmc: Successfully tuned phase to >> > 175 [????3.571742] mmc2: new HS200 MMC card at address 0001 >> > [????3.571943] mmcblk2: mmc2:0001 HAG2e 14.7 GiB? >> > [????3.572026] mmcblk2boot0: mmc2:0001 HAG2e partition 1 4.00 MiB >> > [????3.572107] mmcblk2boot1: mmc2:0001 HAG2e partition 2 4.00 MiB >> > [????3.572181] mmcblk2rpmb: mmc2:0001 HAG2e partition 3 4.00 MiB >> > [????3.685647] mmcblk2: error -110 transferring data, sector 0, nr 8, cmd >> > response 0x900, card status 0x0 >> > And sometimes works, with: >> > [????3.451058] dwmmc_rockchip ff0f0000.dwmmc: Successfully tuned phase to >> > 176 [????3.491093] mmc2: new HS200 MMC card at address 0001 >> > [????3.491277] mmcblk2: mmc2:0001 HAG2e 14.7 GiB? >> > [????3.491345] mmcblk2boot0: mmc2:0001 HAG2e partition 1 4.00 MiB >> > [????3.491409] mmcblk2boot1: mmc2:0001 HAG2e partition 2 4.00 MiB >> > [????3.491474] mmcblk2rpmb: mmc2:0001 HAG2e partition 3 4.00 MiB >> > [????3.493548]??mmcblk2: p1 p2 This is similar behavior to my veyron-speedy. Here are several boot logs
