From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-usb@vger.kernel.org
Cc: Yehezkel Bernat <YehezkelShB@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Gil Fine <gil.fine@intel.com>,
Casey G Bowman <casey.g.bowman@intel.com>,
Andreas Noever <andreas.noever@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 0/8] thunderbolt: Add credit allocation for USB4 devices
Date: Tue, 18 May 2021 17:09:54 +0300 [thread overview]
Message-ID: <20210518141002.63616-1-mika.westerberg@linux.intel.com> (raw)
Hi all,
USB4 spec requires that routers expose their credit (buffer) allocation
preferences through a special router operation. Furthermore the Connection
Manager guide (as part of the USB4 spec bundle) provides some guidance how
the credits should be allocated between different tunneled protocols. This
series adds the credit allocation support for USB4 routers. For Intel
Thunderbolt 1-3 devices we keep using the existing hard-coded scheme.
We also add some KUnit tests for the credit allocation.
Mika Westerberg (8):
thunderbolt: Make tb_port_type() take const parameter
thunderbolt: Move nfc_credits field to struct tb_path_hop
thunderbolt: Wait for the lanes to actually bond
thunderbolt: Read router preferred credit allocation information
thunderbolt: Update port credits after bonding is enabled/disabled
thunderbolt: Allocate credits according to router preferences
thunderbolt: Add quirk for Intel Goshen Ridge DP credits
thunderbolt: Add KUnit tests for credit allocation
drivers/thunderbolt/path.c | 4 +-
drivers/thunderbolt/quirks.c | 29 +-
drivers/thunderbolt/switch.c | 151 +++++++++-
drivers/thunderbolt/tb.h | 44 ++-
drivers/thunderbolt/tb_regs.h | 1 +
drivers/thunderbolt/test.c | 545 ++++++++++++++++++++++++++++++++++
drivers/thunderbolt/tunnel.c | 401 ++++++++++++++++++++-----
drivers/thunderbolt/tunnel.h | 2 +
drivers/thunderbolt/usb4.c | 155 ++++++++++
drivers/thunderbolt/xdomain.c | 10 +
10 files changed, 1253 insertions(+), 89 deletions(-)
--
2.30.2
next reply other threads:[~2021-05-18 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 14:09 Mika Westerberg [this message]
2021-05-18 14:09 ` [PATCH 1/8] thunderbolt: Make tb_port_type() take const parameter Mika Westerberg
2021-05-18 14:09 ` [PATCH 2/8] thunderbolt: Move nfc_credits field to struct tb_path_hop Mika Westerberg
2021-05-18 14:09 ` [PATCH 3/8] thunderbolt: Wait for the lanes to actually bond Mika Westerberg
2021-05-18 14:09 ` [PATCH 4/8] thunderbolt: Read router preferred credit allocation information Mika Westerberg
2021-05-18 14:09 ` [PATCH 5/8] thunderbolt: Update port credits after bonding is enabled/disabled Mika Westerberg
2021-05-18 14:10 ` [PATCH 6/8] thunderbolt: Allocate credits according to router preferences Mika Westerberg
2021-05-18 14:10 ` [PATCH 7/8] thunderbolt: Add quirk for Intel Goshen Ridge DP credits Mika Westerberg
2021-05-18 14:10 ` [PATCH 8/8] thunderbolt: Add KUnit tests for credit allocation Mika Westerberg
2021-06-01 7:50 ` [PATCH 0/8] thunderbolt: Add credit allocation for USB4 devices 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=20210518141002.63616-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=casey.g.bowman@intel.com \
--cc=gil.fine@intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.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 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.