From: "Antti Järvinen" <antti.jarvinen@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Antti Järvinen" <antti.jarvinen@gmail.com>
Subject: [PATCH] PCI: quirk for preventing bus reset on TI C667X
Date: Tue, 12 Jan 2021 15:36:43 +0000 [thread overview]
Message-ID: <20210112153643.17930-1-antti.jarvinen@gmail.com> (raw)
TI C667X does not support bus/hot reset.
See https://e2e.ti.com/support/processors/f/791/t/954382
Signed-off-by: Antti Järvinen <antti.jarvinen@gmail.com>
---
drivers/pci/quirks.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 653660e3ba9e..c8fcf24c5bd0 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -3578,6 +3578,12 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATHEROS, 0x0034, quirk_no_bus_reset);
*/
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_CAVIUM, 0xa100, quirk_no_bus_reset);
+/*
+ * Some TI keystone C667X devices do no support bus/hot reset.
+ * https://e2e.ti.com/support/processors/f/791/t/954382
+ */
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_TI, 0xb005, quirk_no_bus_reset);
+
static void quirk_no_pm_reset(struct pci_dev *dev)
{
/*
--
2.17.1
next reply other threads:[~2021-01-12 15:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 15:36 Antti Järvinen [this message]
2021-01-21 23:55 ` Bjorn Helgaas
2021-01-26 11:22 ` Antti Järvinen
2021-01-29 23:49 ` Bjorn Helgaas
2021-02-17 21:18 ` Bjorn Helgaas
2021-02-28 13:53 ` [PATCH v2] " Antti Järvinen
2021-03-07 0:22 ` Krzysztof Wilczyński
2021-03-08 14:21 ` [PATCH v3] PCI: Add " Antti Järvinen
2021-03-12 21:09 ` Bjorn Helgaas
2021-03-15 10:26 ` [PATCH v4] " Antti Järvinen
2021-04-19 12:44 ` Kishon Vijay Abraham I
2021-05-27 23:07 ` Bjorn Helgaas
2021-03-15 10:45 ` [PATCH v3] " Antti Järvinen
2021-03-08 14:28 ` [PATCH v2] PCI: " Antti Järvinen
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=20210112153643.17930-1-antti.jarvinen@gmail.com \
--to=antti.jarvinen@gmail.com \
--cc=bhelgaas@google.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
all inboxes | Powered by JetHome®