From: Jan-Jaap van der Heijden <janjaap@daptechnology.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] firewire: ohci: enable SLLZ059 erratum with XIO2213 OHCI chip
Date: Fri, 11 Dec 2020 14:12:26 +0100 [thread overview]
Message-ID: <e86c724b-009b-9f3b-3c1e-0804ac4c7a2b@daptechnology.com> (raw)
The XIO2213 PCIe to 1394b OHCI controller can be used with an external
PHY chip instead of the built-in one. In order to support the combination
of the XIO2213 with a TSB41BA3D PHY chip, we need to enable the SLLZ059
erratum for the XIO2213 like we do for other TI 1394 link layer chips.
Signed-off-by: Jan-Jaap van der Heijden <janjaap@daptechnology.com>
Signed-off-by: Jeroen de Zoeten <jeroen@daptechnology.com>
---
ohci.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/firewire/ohci.c b/drivers/firewire/ohci.c
index 9811c40956e5..142511a57a05 100644
--- a/drivers/firewire/ohci.c
+++ b/drivers/firewire/ohci.c
@@ -267,6 +267,7 @@ static char ohci_driver_name[] = KBUILD_MODNAME;
#define PCI_DEVICE_ID_TI_TSB12LV22 0x8009
#define PCI_DEVICE_ID_TI_TSB12LV26 0x8020
#define PCI_DEVICE_ID_TI_TSB82AA2 0x8025
+#define PCI_DEVICE_ID_TI_XIO2213 0x823f
#define PCI_DEVICE_ID_VIA_VT630X 0x3044
#define PCI_REV_ID_VIA_VT6306 0x46
#define PCI_DEVICE_ID_VIA_VT6315 0x3403
@@ -316,6 +317,9 @@ static const struct {
{PCI_VENDOR_ID_TI, PCI_DEVICE_ID_TI_TSB82AA2, PCI_ANY_ID,
QUIRK_RESET_PACKET | QUIRK_TI_SLLZ059},
+ {PCI_VENDOR_ID_TI, PCI_DEVICE_ID_TI_XIO2213, PCI_ANY_ID,
+ QUIRK_RESET_PACKET | QUIRK_TI_SLLZ059},
+
{PCI_VENDOR_ID_TI, PCI_ANY_ID, PCI_ANY_ID,
QUIRK_RESET_PACKET},
reply other threads:[~2020-12-11 13:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e86c724b-009b-9f3b-3c1e-0804ac4c7a2b@daptechnology.com \
--to=janjaap@daptechnology.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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).