From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-usb@vger.kernel.org
Cc: Michael Jamet <michael.jamet@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andreas Noever <andreas.noever@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
netdev@vger.kernel.org
Subject: [PATCH 0/5] thunderbolt: net: Enable full end-to-end flow control
Date: Tue, 30 Aug 2022 18:32:45 +0300 [thread overview]
Message-ID: <20220830153250.15496-1-mika.westerberg@linux.intel.com> (raw)
Hi all,
Thunderbolt/USB4 host controllers support full end-to-end flow control
that prevents dropping packets if there are not enough hardware receive
buffers. So far it has not been enabled for the networking driver yet
but this series changes that. There is one snag though: the second
generation (Intel Falcon Ridge) had a bug that needs special quirk to
get it working. We had that in the early stages of the Thunderbolt/USB4
driver but it got dropped because it was not needed at the time. Now we
add it back as a quirk for the host controller (NHI).
The first patch of this series is a bugfix that I'm planning to push for
v6.0-rc. Rest are v6.1 material. This also includes a patch that shows
the XDomain link type in sysfs the same way we do for USB4 routers and
updates the networking driver module description.
Mika Westerberg (5):
net: thunderbolt: Enable DMA paths only after rings are enabled
thunderbolt: Show link type for XDomain connections too
thunderbolt: Add back Intel Falcon Ridge end-to-end flow control workaround
net: thunderbolt: Enable full end-to-end flow control
net: thunderbolt: Update module description with mention of USB4
drivers/net/thunderbolt.c | 62 +++++++++++++++++++++------------
drivers/thunderbolt/nhi.c | 49 ++++++++++++++++++++++----
drivers/thunderbolt/tb.c | 8 ++---
drivers/thunderbolt/tb.h | 2 +-
drivers/thunderbolt/usb4.c | 8 +++--
drivers/thunderbolt/usb4_port.c | 2 ++
include/linux/thunderbolt.h | 2 ++
7 files changed, 96 insertions(+), 37 deletions(-)
--
2.35.1
next reply other threads:[~2022-08-30 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 15:32 Mika Westerberg [this message]
2022-08-30 15:32 ` [PATCH 1/5] net: thunderbolt: Enable DMA paths only after rings are enabled Mika Westerberg
2022-08-30 15:32 ` [PATCH 2/5] thunderbolt: Show link type for XDomain connections too Mika Westerberg
2022-08-30 15:32 ` [PATCH 3/5] thunderbolt: Add back Intel Falcon Ridge end-to-end flow control workaround Mika Westerberg
2022-08-30 15:32 ` [PATCH 4/5] net: thunderbolt: Enable full end-to-end flow control Mika Westerberg
2022-08-30 15:32 ` [PATCH 5/5] net: thunderbolt: Update module description with mention of USB4 Mika Westerberg
2022-08-31 13:20 ` [PATCH 0/5] thunderbolt: net: Enable full end-to-end flow control patchwork-bot+netdevbpf
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=20220830153250.15496-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).