[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181114003345.GV2089@sirena.org.uk>
Date: Tue, 13 Nov 2018 16:33:45 -0800
From: Mark Brown <broonie@...nel.org>
To: Peter Ujfalusi <peter.ujfalusi@...com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
linux-usb@...r.kernel.org, Felipe Balbi <balbi@...nel.org>,
Guenter Roeck <linux@...ck-us.net>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Roger Quadros <rogerq@...com>, linux-pm@...r.kernel.org,
"Rafael J. Wysocki" <rafael@...nel.org>,
Sebastian Reichel <sre@...nel.org>, linux-omap@...r.kernel.org,
Darren Hart <dvhart@...radead.org>,
platform-driver-x86@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, Chen-Yu Tsai <wens@...e.org>,
Hans de Goede <hdegoede@...hat.com>,
Grant Likely <grant.likely@...aro.org>,
Andrzej Hajda <a.hajda@...sung.com>
Subject: Re: [PATCH v1 1/5] drivercore: Revert "deferral race condition fix"
On Mon, Nov 12, 2018 at 06:11:26PM +0200, Peter Ujfalusi wrote:
> if we revert the commit then the original issue will re-surfaces. afaik
> it was not only audio which hit the 'last driver to be probed from the
> deferred list would never probe, unless we provoke the kernel to load
> additional module, or remove/reload the module' issue.
Right, aren't we just going to be swapping one bug for another?
> Do I understand correctly that in your case you have two modules
> (dwc3-pci and extcon-intel-mrfld) in a deferred probe loop, iow both of
> the drivers returns -EPROBE_DEFER and they just spin?
> If both is deferring, how this supposed to work?
I'm struggling to follow the original explanation too :(
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists