* Kevin Hilman <khilman@xxxxxxxxxx> [150910 10:03]: > On Tue, Sep 1, 2015 at 8:03 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > * Grygorii Strashko <grygorii.strashko@xxxxxx> [150901 07:57]: > >> On 09/01/2015 05:50 PM, Tony Lindgren wrote: > >> >> > >> >>On -next, Above crash signature could be related to race > >> >>"ARM: OMAP2+: omap-device: fix race deferred probe of omap_hsmmc vs omap_device_late_init" > >> >>http://www.spinics.net/lists/linux-omap/msg121622.html > >> > > >> >Good point thanks, yes that's the case. MMC probing fails and then we hit this > >> >separate issue while MMC is trying to probe. Applying your fix makes the > >> >abort disappear, but naturally does not get MMC working again. > >> > >> you may need CONFIG_GPIO_PCF857X=y for dra7-evm > > > > This is a regression at least on omap4 as pointed out by Olof. > > FWIW, this problem still exists in mainline[1], and note that it fails > for omap2plus_defconfig which already has CONFIG_REGULATOR_PBIAS=y, so > that is not the fix for this issue. There are also the pbias regulator fixes pending.. And the .dts fixes pending.. So looks like it's going to be few more days. AFAIK, also the multi_v7_defconfig change is needed.. Regards, Tony > [1] http://kernelci.org/boot/omap4-panda-es/?mainline&omap2plus_defconfig&lab-khilman -- 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
