All of lore.kernel.org
 help / color / mirror / Atom feed
From: Barto <mister.freeman@laposte.net>
To: Bjorn Helgaas <bhelgaas@google.com>,
	"Liu, Chuansheng" <chuansheng.liu@intel.com>
Cc: "Tejun Heo (tj@kernel.org)" <tj@kernel.org>,
	"Lu, Aaron" <aaron.lu@intel.com>,
	Rafael Wysocki <rjw@rjwysocki.net>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: Do not enable async suspend for JMicron chips
Date: Thu, 06 Nov 2014 06:29:43 +0100	[thread overview]
Message-ID: <545B0747.2030201@laposte.net> (raw)
In-Reply-To: <CAErSpo4py1GdxczyzgLxjbgmfGEQ6o+He=7wxuVS0BM-Oyd6_w@mail.gmail.com>

Hello Bjorn,

in my bugreport I have already tried to add the JMicron 368 in the "if
statement" and it didn't work, check my message here :

https://bugzilla.kernel.org/show_bug.cgi?id=84861#c11

if Chuansheng has choosen a more generic way ( applying the patch to all
JMicron devices  ) it's because also because we don't know how many
JMBxxx models could be affected by this bug, tomorrow maybe one user
would create a bug report about a "JMB369" pci card who have again this
bug, and maybe on month later another user with a "JMB382", it could be
a nightmare for Chuanseng if he had to create every time a new patch for
each model of JMicron,

so for the moment the better approach for me is to disable async_suspend
for all JMBxxx JMicron, Chuanseng's patch seems reasonnable, as long as
we don't know the exact list of JMBxxx models we can assume that all
JMicron SATA/IDE are affected by this problem


Le 06/11/2014 05:08, Bjorn Helgaas a écrit :

> 
> But you haven't addressed my concerns about (1) putting a PCI vendor
> ID check in the generic PCI core code, and (2) applying this to *all*
> JMicron devices.  You might want to explore a quirk-type solution or
> maybe just add the JMicron 368 to the checks added by e6b7e41cdd8c.
> 
> Bjorn
> 

  reply	other threads:[~2014-11-06  5:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05  1:31 [PATCH] PCI: Do not enable async suspend for JMicron chips Chuansheng Liu
2014-11-05 18:01 ` Bjorn Helgaas
2014-11-05 18:46   ` Barto
2014-11-05 19:03     ` Bjorn Helgaas
2014-11-06  1:36       ` Barto
2014-11-06  1:48       ` Liu, Chuansheng
2014-11-06  1:48         ` Liu, Chuansheng
2014-11-06  4:08         ` Bjorn Helgaas
2014-11-06  5:29           ` Barto [this message]
2014-11-06  5:29           ` Liu, Chuansheng
2014-11-06  5:29             ` Liu, Chuansheng
2014-11-06  5:36             ` Aaron Lu
2014-11-06  6:39               ` Liu, Chuansheng
2014-11-06  6:39                 ` Liu, Chuansheng
2014-11-06  8:25                 ` Barto
2014-11-06 17:39                 ` Bjorn Helgaas
2014-11-06 21:02                   ` Barto
2014-11-07  1:09                   ` Liu, Chuansheng
2014-11-07  1:09                     ` Liu, Chuansheng
  -- strict thread matches above, loose matches on Subject: below --
2014-11-05  1:07 Chuansheng Liu
2014-11-05  1:33 ` Aaron Lu
2014-11-05  1:35   ` Aaron Lu
2014-11-05 16:31 ` Tejun Heo
2014-11-05 17:58   ` Barto
2014-11-05 18:04   ` Tejun Heo

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=545B0747.2030201@laposte.net \
    --to=mister.freeman@laposte.net \
    --cc=aaron.lu@intel.com \
    --cc=bhelgaas@google.com \
    --cc=chuansheng.liu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --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.