From: Bjorn Helgaas <helgaas@kernel.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Add function 1 DMA alias quirk for Marvell 9170 SATA controller
Date: Fri, 5 Apr 2019 16:13:33 -0500 [thread overview]
Message-ID: <20190405211333.GA159318@google.com> (raw)
In-Reply-To: <20190405152047.153417-1-andre.przywara@arm.com>
On Fri, Apr 05, 2019 at 04:20:47PM +0100, Andre Przywara wrote:
> There is a Marvell 88SE9170 PCIe SATA controller I found on a board
> here. Some quick testing with the ARM SMMU enabled reveals that it
> suffers from the same requester ID mixup problems as the other Marvell
> chips listed already.
>
> Add the PCI vendor/device ID to the list of chips which need the
> workaround.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Applied with stable tag to for-linus for v5.1, thanks!
> ---
> drivers/pci/quirks.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index a59ad09ce911..a077f67fe1da 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -3877,6 +3877,8 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x9128,
> /* https://bugzilla.kernel.org/show_bug.cgi?id=42679#c14 */
> DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x9130,
> quirk_dma_func1_alias);
> +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x9170,
> + quirk_dma_func1_alias);
> /* https://bugzilla.kernel.org/show_bug.cgi?id=42679#c47 + c57 */
> DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x9172,
> quirk_dma_func1_alias);
> --
> 2.17.1
>
prev parent reply other threads:[~2019-04-05 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 15:20 [PATCH] PCI: Add function 1 DMA alias quirk for Marvell 9170 SATA controller Andre Przywara
2019-04-05 21:13 ` Bjorn Helgaas [this message]
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=20190405211333.GA159318@google.com \
--to=helgaas@kernel.org \
--cc=andre.przywara@arm.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 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).