From: Tejun Heo <tj@kernel.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-pci <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
chuansheng.liu@intel.com, Alan Stern <stern@rowland.harvard.edu>,
Aaron Lu <aaron.lu@intel.com>,
MyMailClone@t-online.de, mister.freeman@laposte.net,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] PCI: Disable async suspend/resume for Jmicron chip
Date: Tue, 28 Jul 2015 13:58:48 -0400 [thread overview]
Message-ID: <20150728175848.GI5322@mtj.duckdns.org> (raw)
In-Reply-To: <1438047747.1856.12.camel@rzhang1-mobl4>
On Tue, Jul 28, 2015 at 09:42:27AM +0800, Zhang Rui wrote:
> From 57edba9c677e47354846db951014dc4d5b13ce54 Mon Sep 17 00:00:00 2001
> From: Zhang Rui <rui.zhang@intel.com>
> Date: Sun, 26 Jul 2015 14:15:36 +0800
> Subject: [PATCH] PCI: Disable async suspend/resume for Jmicron chip
>
> In https://bugzilla.kernel.org/show_bug.cgi?id=81551,
> we found that Jmicron chip 361/363 is broken after resume if async noirq
> (76569faa62 (PM / sleep: Asynchronous threads for resume_noirq)) is supported,
> thus commit e6b7e41cdd (ata: Disabling the async PM for JMicron chip 363/361)
> is introduced to fix this problem.
> But then, we found that Jmicron chip 368 also has this problem, and it is decided
> to disable the pm async feature for all the Jmicron chips.
>
> But how to fix this was discussed in the mailing list for some time.
> After some investigation, we believe that a proper fix is to disable
> the async PM in PCI instead of ata driver, because, on this platform,
> pci_resume_noirq() of IDE controller must happen after pci_resume_noirq()
> of AHCI controller. But as .resume_noirq() of the pata_jmicron driver is
> no-op, this suggests that it is the PCI common actions, aka,
> pci_pm_default_resume_early(), have the dependency.
> To fix this, using device_pm_wait_for_dev() in pata_jmicron driver can not
> solve the dependency because pci_pm_default_resume_early() is invoked before
> driver callback being invoked, plus, as it is the PCI common actions that
> have the dependency, it is reasonable to fix it in PCI bus code,
> rather than driver code.
>
> This patch is made based on the patch from Liu Chuansheng at
> https://lkml.org/lkml/2014/12/5/74
> it reverts commit e6b7e41cdd ("ata: Disabling the async PM for JMicron
> chip 363/361"), and introduces a PCI quirk to disable async PM for Jmicron
> chips.
>
> Reference: https://bugzilla.kernel.org/show_bug.cgi?id=81551
> Tested-by: Jay <MyMailClone@t-online.de>
> Tested-by: Barto <mister.freeman@laposte.net>
> Signed-off-by: Zhang Rui <rui.zhang@intel.com>
Acked-by: Tejun Heo <tj@kernel.org>
> /*
> + * For JMicron chips, we need to disable the async_suspend method, otherwise
> + * they will hit the power-on issue when doing device resume, add one quick
> + * solution to disable the async_suspend method.
> + */
Maybe add a link to the bug report and/or discussion thread?
Thanks.
--
tejun
next prev parent reply other threads:[~2015-07-28 17:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 1:42 [PATCH] PCI: Disable async suspend/resume for Jmicron chip Zhang Rui
2015-07-28 1:48 ` Liu, Chuansheng
2015-07-28 2:06 ` Aaron Lu
2015-07-28 17:58 ` Tejun Heo [this message]
2015-07-29 1:39 ` Zhang Rui
2015-08-14 20:17 ` Bjorn Helgaas
[not found] ` <3296684.6OYqAkrTIu@linux-tez8>
2015-08-15 14:39 ` Bjorn Helgaas
[not found] ` <143984396.fBJoMvWU1G@linux-tez8>
2015-08-15 20:57 ` Bjorn Helgaas
2015-08-15 16:57 ` Zhang Rui
2015-08-15 21:45 ` Bjorn Helgaas
2015-08-15 23:40 ` Barto
2015-08-25 2:49 ` Bjorn Helgaas
2015-08-25 20:21 ` Yinghai Lu
2015-08-25 20:50 ` Bjorn Helgaas
2015-08-28 8:21 ` Zhang Rui
2015-08-28 17:53 ` Barto
2015-08-28 18:30 ` Barto
[not found] ` <2907359.7nsusuUeG0@linux-tez8>
2015-08-28 18:50 ` Barto
2015-08-28 19:19 ` Bjorn Helgaas
2015-08-28 20:36 ` Barto
2015-08-28 20:54 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150728175848.GI5322@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=MyMailClone@t-online.de \
--cc=aaron.lu@intel.com \
--cc=bhelgaas@google.com \
--cc=chuansheng.liu@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=mister.freeman@laposte.net \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).