On Wed, 2015-06-10 at 02:08 +0200, Rafael J. Wysocki wrote: > On Tuesday, June 09, 2015 01:42:00 AM Rafael J. Wysocki wrote: > > On Monday, June 01, 2015 05:47:57 PM Andy Shevchenko wrote: > > > From: Heikki Krogerus <heikki.krogerus@xxxxxxxxxxxxxxx> > > > > > > If the parent is still suspended when driver probe is > > > attempted, the result may be failure. > > > > > > For example, if the parent is a PCI MFD device that has been > > > suspended when we try to probe our device, any register > > > reads will return 0xffffffff. > > > > > > To fix the problem, making sure the parent is always awake > > > before attempting driver probe. [] > Actually, something like the below should work too (the bumping up of the > parent's usage counter before the loop will keep it in the runtime-active > state throughout the loop). It works. Thanks for the patch. We incorporate it instead of the previous Heikki's patch into v4. -- Andy Shevchenko <andriy.shevchenko@xxxxxxxxx> Intel Finland Oy -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
