On Mon, Sep 01, 2014 at 08:38:03AM +0800, Chuansheng Liu wrote: > After enabled the PM feature that supporting async noirq(76569faa62 > (PM / sleep: Asynchronous threads for resume_noirq)), > Jay hit the system resuming issue, that one of the JMicron controller > can not be powered up. > > His device tree is like below: > +-1c.4-[02]--+-00.0 JMicron Technology Corp. JMB363 SATA/IDE > Controller > | \-00.1 JMicron Technology Corp. JMB363 SATA/IDE > Controller > > After investigation, we found the the Micron chip 363 included > one SATA controller(0000:02:00.0) and one PATA controller(0000:02:00.1), > these two controllers do not have parent-children relationship, > but the PATA controller only can be powered on after the SATA controller > has finished the powering on. > > If we enabled the async noirq(), then the below error is hit during noirq > phase: > pata_jmicron 0000:02:00.1: Refused to change power state, currently in D3 > > Here for JMicron chip 363/361, we need forcedly to disable the async method. > > Bug detail: https://bugzilla.kernel.org/show_bug.cgi?id=81551 > > Reported-by: Jay <[email protected]> > Signed-off-by: Chuansheng Liu <[email protected]>
Applied to libata/for-3.17-fixes. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
