From: Bjorn Helgaas <bhelgaas@google.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Add bridge DMA alias quirk for Intel 82801
Date: Sat, 5 Jul 2014 10:31:43 -0600 [thread overview]
Message-ID: <20140705163143.GB6247@google.com> (raw)
In-Reply-To: <20140623223530.13445.94886.stgit@gimli.home>
On Mon, Jun 23, 2014 at 04:36:25PM -0600, Alex Williamson wrote:
> This bridge sometimes shows up as a root complex device and sometimes
> as a discrete PCIe-to-PCI bridge. Testing indicates that in the
> latter case, we need to enable the PCIe bridge DMA alias quirk.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> Reported-by: Milos Kaurin <milos.kaurin@gmail.com>
> Tested-by: Milos Kaurin <milos.kaurin@gmail.com>
Applied to for-linus for v3.16, thanks!
> ---
>
> drivers/pci/quirks.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index 78a7df6..460c354 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -3405,6 +3405,8 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ASMEDIA, 0x1080,
> DECLARE_PCI_FIXUP_HEADER(0x10e3, 0x8113, quirk_use_pcie_bridge_dma_alias);
> /* ITE 8892, https://bugzilla.kernel.org/show_bug.cgi?id=73551 */
> DECLARE_PCI_FIXUP_HEADER(0x1283, 0x8892, quirk_use_pcie_bridge_dma_alias);
> +/* Intel 82801, https://bugzilla.kernel.org/show_bug.cgi?id=44881#c49 */
> +DECLARE_PCI_FIXUP_HEADER(0x8086, 0x244e, quirk_use_pcie_bridge_dma_alias);
>
> /*
> * AMD has indicated that the devices below do not support peer-to-peer
>
next prev parent reply other threads:[~2014-07-05 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 22:36 [PATCH] PCI: Add bridge DMA alias quirk for Intel 82801 Alex Williamson
2014-07-05 16:31 ` Bjorn Helgaas [this message]
2014-07-05 21:26 ` Bjorn Helgaas
2014-07-05 21:56 ` Joerg Roedel
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=20140705163143.GB6247@google.com \
--to=bhelgaas@google.com \
--cc=alex.williamson@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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.