From: Sinan Kaya <okaya@codeaurora.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, sulrich@codeaurora.org,
timur@codeaurora.org, linux-arm-msm@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
open list <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PCI: quirk HT1100 & HT2000 and one HT2100 Root Ports for Extended Tags
Date: Tue, 10 Apr 2018 16:18:01 -0400 [thread overview]
Message-ID: <1c94361d-7a8d-ad18-12e5-1612326a54db@codeaurora.org> (raw)
In-Reply-To: <20180410195008.GE54986@bhelgaas-glaptop.roam.corp.google.com>
On 4/10/2018 3:50 PM, Bjorn Helgaas wrote:
> On Tue, Apr 10, 2018 at 02:41:44PM -0500, Bjorn Helgaas wrote:
>> On Wed, Apr 04, 2018 at 06:50:09PM -0400, Sinan Kaya wrote:
>>> Per PCIe r3.1, sec 2.2.6.2 and 7.8.4, a Requester may not use 8-bit Tags
>>> unless its Extended Tag Field Enable is set, but all Receivers/Completers
>>> must handle 8-bit Tags correctly regardless of their Extended Tag Field
>>> Enable.
>>>
>>> Some devices do not handle 8-bit Tags as Completers, so add a quirk for
>>> them. If we find such a device, we disable Extended Tags for the entire
>>> hierarchy to make peer-to-peer DMA possible.
>>>
>>> The Broadcom HT1100/HT2000/HT2100 seems to have issues with handling 8-bit
>>> tags. Mark it as broken.
>>>
>>> Fixes: 60db3a4d8cc9 ("PCI: Enable PCIe Extended Tags if supported")
>>> Link: https://bugzilla.kernel.org/show_bug.cgi?id=196197
>>> Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
>> Applied to pci/enumeration for v4.18, thanks!
> Actually, this is a really annoying issue and I think the fix is
> appropriate for v4.17, so I moved it to my for-linus branch.
>
I agree. It causes boot issues on some AMD Opteron machines. It should
probably be back-ported too.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-04-10 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 22:50 [PATCH] PCI: quirk HT1100 & HT2000 and one HT2100 Root Ports for Extended Tags Sinan Kaya
2018-04-10 19:41 ` Bjorn Helgaas
2018-04-10 19:50 ` Bjorn Helgaas
2018-04-10 20:18 ` Sinan Kaya [this message]
2018-04-11 13:51 ` Bjorn Helgaas
2018-04-11 14:02 ` Sinan Kaya
2018-04-11 14:08 ` Greg Kroah-Hartman
2018-04-11 14:13 ` Sinan Kaya
2018-04-11 14:19 ` Greg Kroah-Hartman
2018-04-11 16:23 ` Sinan Kaya
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=1c94361d-7a8d-ad18-12e5-1612326a54db@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sulrich@codeaurora.org \
--cc=timur@codeaurora.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).