[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150901150336.GF4215@atomide.com>
Date: Tue, 1 Sep 2015 08:03:36 -0700
From: Tony Lindgren <tony@...mide.com>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: Kishon Vijay Abraham I <kishon@...com>,
Olof Johansson <olof@...om.net>,
Ulf Hansson <ulf.hansson@...aro.org>, afenkart@...il.com,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
linux-omap <linux-omap@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sekhar Nori <nsekhar@...com>, Neil Brown <neilb@...e.de>
Subject: Re: [PATCH v3 02/15] mmc: host: omap_hsmmc: return on fatal errors
from omap_hsmmc_reg_get
* Grygorii Strashko <grygorii.strashko@...com> [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.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists