On Saturday, September 13, 2014 01:53:55 AM Fu, Zhonghui wrote: > > On 2014/9/10 15:50, Mika Westerberg wrote: > > On Tue, Sep 09, 2014 at 01:36:48PM +0800, Fu, Zhonghui wrote: > >> >From 6deb00230f5df68da3ca7490402a0c537bf386bb Mon Sep 17 00:00:00 2001 > >> From: Fu Zhonghui <zhonghui.fu@xxxxxxxxxxxxxxx> > >> Date: Tue, 9 Sep 2014 13:02:25 +0800 > >> Subject: [PATCH] ACPI / platform / LPSS: disable async suspend/resume of LPSS devices > >> > >> LPSS devices must suspend/resume in fixed order. Or some LPSS devices > >> will hang during the transition to ACPI_STATE_D0 state. > > In addition to the comment from Rafael, I would like to have more > > details here why we must suspend/resume the LPSS devices in certain > > order. > Sorry for late response. > > After the patch "ACPI / platform / LPSS: Enable async suspend/resume of LPSS devices(commit ID: 8ce62f85a81f57e86bc120ab690facc612223188)" was merged into upstream kernel, some LPSS devices(UART, I2C) frequently hang during resume. So, my patch is actually reverting that patch. I suppose the Mika's question was more about whether or not you were able to identify the exact reason why the LPSS devices in question stopped resuming correctly after the above change. Also, your patch is not actually revering the whole commit mentioned above, as it did a couple of things more. You're simply restoring the previous behavior, which doesn't mean "reverting". -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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
