From: Barto <mister.freeman@laposte.net>
To: Bjorn Helgaas <bhelgaas@google.com>, Zhang Rui <rui.zhang@intel.com>
Cc: Tejun Heo <tj@kernel.org>, linux-pci <linux-pci@vger.kernel.org>,
chuansheng.liu@intel.com, Alan Stern <stern@rowland.harvard.edu>,
Aaron Lu <aaron.lu@intel.com>,
MyMailClone@t-online.de, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] PCI: Disable async suspend/resume for Jmicron chip
Date: Sun, 16 Aug 2015 01:40:05 +0200 [thread overview]
Message-ID: <55CFCDD5.6040302@laposte.net> (raw)
In-Reply-To: <20150814201752.GG26431@google.com>
Le 14/08/2015 22:17, Bjorn Helgaas a écrit :
> For 1), I think it is probably overkill to penalize all JMicron
> devices. There's no reason to think NICs and SD/MMC/etc controllers
> have the same issue. Or if there *is* reason to think that, you
> should give evidence for it.
if you don't want to penalize all JMicron models then a workaround would
be to create a new feature : the ability for the user to disable async
for a specific device,
for example a kernel parameter ( no-async-for-jmicron ), or a more
configurable mechanism, like a configuration file where the user can add
the name of the device, a kind of blacklist in order to disable async
only for a list of devices,
it's only a workaround, the real solution would to be find the real root
cause ( a bug in async method ? a design flaw in JMicron hardware ? a
bios/acpi bug ? )
next prev parent reply other threads:[~2015-08-15 23:47 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
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 [this message]
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=55CFCDD5.6040302@laposte.net \
--to=mister.freeman@laposte.net \
--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=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=stern@rowland.harvard.edu \
--cc=tj@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.