From: Sinan Kaya <okaya@kernel.org>
To: Daniel Drake <drake@endlessm.com>, bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, linux@endlessm.com,
nouveau@lists.freedesktop.org, linux-pm@vger.kernel.org,
peter@lekensteyn.nl, kherbst@redhat.com,
andriy.shevchenko@linux.intel.com, rafael.j.wysocki@intel.com,
keith.busch@intel.com, mika.westerberg@linux.intel.com,
jonathan.derrick@intel.com, kugel@rockbox.org,
davem@davemloft.net, hkallweit1@gmail.com,
netdev@vger.kernel.org, nic_swsd@realtek.com
Subject: Re: [PATCH] PCI: Reprogram bridge prefetch registers on resume
Date: Thu, 6 Sep 2018 23:40:56 -0700 [thread overview]
Message-ID: <3b37e4fd-c793-bd52-7d70-950f846a7d5a@kernel.org> (raw)
In-Reply-To: <20180907053614.6540-1-drake@endlessm.com>
On 9/6/2018 10:36 PM, Daniel Drake wrote:
> + if (pci_dev->class == PCI_CLASS_BRIDGE_PCI << 8)
> + pci_setup_bridge_mmio_pref(pci_dev);
This should probably some kind of a quirk rather than default
for the listed card as it sounds like you are dealing with
broken hardware.
next prev parent reply other threads:[~2018-09-07 11:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 5:36 [PATCH] PCI: Reprogram bridge prefetch registers on resume Daniel Drake
2018-09-07 5:36 ` Daniel Drake
2018-09-07 5:49 ` [Nouveau] " Lukas Wunner
2018-09-07 6:40 ` Sinan Kaya [this message]
[not found] ` <3b37e4fd-c793-bd52-7d70-950f846a7d5a-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-09-07 8:06 ` Daniel Drake
2018-09-07 8:06 ` Daniel Drake
[not found] ` <20180907053614.6540-1-drake-6IF/jdPJHihWk0Htik3J/w@public.gmane.org>
2018-09-07 15:05 ` Peter Wu
2018-09-07 15:05 ` Peter Wu
2018-09-07 22:26 ` Bjorn Helgaas
2018-09-08 12:14 ` Peter Wu
2018-09-08 11:05 ` Thomas Martitz
2018-09-08 11:05 ` Thomas Martitz
2018-09-11 3:35 ` Daniel Drake
2018-09-11 3:35 ` Daniel Drake
2018-09-11 9:08 ` Rafael J. Wysocki
2018-09-10 19:57 ` Thomas Martitz
2018-09-10 19:57 ` Thomas Martitz
2018-09-07 21:48 ` 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=3b37e4fd-c793-bd52-7d70-950f846a7d5a@kernel.org \
--to=okaya@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=drake@endlessm.com \
--cc=hkallweit1@gmail.com \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=kherbst@redhat.com \
--cc=kugel@rockbox.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=nouveau@lists.freedesktop.org \
--cc=peter@lekensteyn.nl \
--cc=rafael.j.wysocki@intel.com \
/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.