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>,
Lukas Wunner <lukas@wunner.de>,
Andreas Noever <andreas.noever@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 0/3] thunderbolt: Improvements for Alpine and Titan Ridge devices
Date: Wed, 26 Jan 2022 17:16:50 +0300 [thread overview]
Message-ID: <20220126141653.28092-1-mika.westerberg@linux.intel.com> (raw)
Hi all,
The first two patches implement flows that are needed to bring up the
internal xHCI controller when there is USB device connected to the
downstream Thunderbolt port of the the router. The last patch disables
LTTPR (LT-tunable PHY Repeater, DisplayPort term) when Titan Ridge device
router is connected to avoid tunneling issues.
Mika Westerberg (3):
thunderbolt: Add missing device ID to tb_switch_is_alpine_ridge()
thunderbolt: Add internal xHCI connect flows for Thunderbolt 3 devices
thunderbolt: Disable LTTPR on Intel Titan Ridge
drivers/thunderbolt/lc.c | 110 ++++++++++++++++++++++++++++++++++
drivers/thunderbolt/switch.c | 71 +++++++++++++++++++++-
drivers/thunderbolt/tb.c | 11 ++++
drivers/thunderbolt/tb.h | 8 +++
drivers/thunderbolt/tb_regs.h | 9 +++
drivers/thunderbolt/tunnel.c | 10 ++++
6 files changed, 218 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2022-01-26 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 14:16 Mika Westerberg [this message]
2022-01-26 14:16 ` [PATCH 1/3] thunderbolt: Add missing device ID to tb_switch_is_alpine_ridge() Mika Westerberg
2022-01-26 14:16 ` [PATCH 2/3] thunderbolt: Add internal xHCI connect flows for Thunderbolt 3 devices Mika Westerberg
2022-01-27 10:00 ` Lukas Wunner
2022-01-26 14:16 ` [PATCH 3/3] thunderbolt: Disable LTTPR on Intel Titan Ridge Mika Westerberg
2022-02-02 10:59 ` [PATCH 0/3] thunderbolt: Improvements for Alpine and Titan Ridge 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=20220126141653.28092-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.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 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).