From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-usb@vger.kernel.org
Cc: Yehezkel Bernat <YehezkelShB@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
Andreas Noever <andreas.noever@gmail.com>,
Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 0/5] thunderbolt: USB4STREAM improvements
Date: Tue, 28 Jul 2026 13:51:36 +0200 [thread overview]
Message-ID: <20260728115141.2585464-1-mika.westerberg@linux.intel.com> (raw)
Hi all,
This series has a couple of non-critical fixes for USB4STREAM driver and
then makes it work better with io_uring. In addition to that we add a busy
polling mode that can be used by applications that need lower latency than
what is possible with the interrupt mode and worker scheduling.
Mika Westerberg (5):
thunderbolt: stream: Restore consumer if copying from iter fails
thunderbolt: stream: Fix possible short reads/writes
thunderbolt: stream: Support IOCB_NOWAIT in non-blocking I/O as well
thunderbolt: Make interrupt optional for rings
thunderbolt: stream: Add support for busy polling
.../ABI/testing/configfs-thunderbolt_stream | 15 +
drivers/thunderbolt/nhi.c | 27 +-
drivers/thunderbolt/stream.c | 256 ++++++++++++++----
include/linux/thunderbolt.h | 2 +
4 files changed, 243 insertions(+), 57 deletions(-)
--
2.50.1
next reply other threads:[~2026-07-28 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 11:51 Mika Westerberg [this message]
2026-07-28 11:51 ` [PATCH 1/5] thunderbolt: stream: Restore consumer if copying from iter fails Mika Westerberg
2026-07-28 11:51 ` [PATCH 2/5] thunderbolt: stream: Fix possible short reads/writes Mika Westerberg
2026-07-28 11:51 ` [PATCH 3/5] thunderbolt: stream: Support IOCB_NOWAIT in non-blocking I/O as well Mika Westerberg
2026-07-28 11:51 ` [PATCH 4/5] thunderbolt: Make interrupt optional for rings Mika Westerberg
2026-07-28 11:51 ` [PATCH 5/5] thunderbolt: stream: Add support for busy polling Mika Westerberg
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=20260728115141.2585464-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=alan.borzeszkowski@linux.intel.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.