From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4] PCI: Add Extended Tags quirk for Broadcom HT2100 Root Port
Date: Wed, 12 Jul 2017 08:15:43 -0400 [thread overview]
Message-ID: <b8ccaffe-d907-db04-a793-86a3b67f61af@codeaurora.org> (raw)
In-Reply-To: <CABawtvMCJy1Y0Cv-NhVRv4qKLiZ-PUWfeZhTA6uGiiiswe+g6A@mail.gmail.com>
On 7/12/2017 5:44 AM, Ethan Zhao wrote:
> The dmesg yelled "...Tag handling is broken" , but didn't say how it
> was handled, that is weird and confusing, just because there is no
> device under that bridge ?
>
> How about move the messages together "...is broken, disable Extended tag..."
This was something requested by Bjorn to inform that user has a broken HW
when a quirk is matched.
The new code will disable extended tags only if it was enabled on endpoint
via power on reset value or via some broken BIOS.
It looks like we are not seeing any disabling message. This implies that
both the card and BIOS is good.
That's why, you are no longer seeing a disabling message on this system
and code is just not enabling extended tags.
--
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:[~2017-07-12 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 4:04 [PATCH V4] PCI: Add Extended Tags quirk for Broadcom HT2100 Root Port Sinan Kaya
2017-07-12 8:55 ` Wim ten Have
2017-07-12 9:44 ` Ethan Zhao
2017-07-12 12:15 ` Sinan Kaya [this message]
2017-07-12 19:34 ` Bjorn Helgaas
2017-07-13 5:54 ` Ethan Zhao
2017-07-12 19:39 ` 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=b8ccaffe-d907-db04-a793-86a3b67f61af@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).