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>,
"Christian Schaubschläger" <christian.schaubschlaeger@gmx.at>,
"Gil Fine" <gil.fine@linux.intel.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>
Subject: [PATCH 0/5] thunderbolt: A couple of fixes
Date: Mon, 6 Mar 2023 13:36:00 +0200 [thread overview]
Message-ID: <20230306113605.46137-1-mika.westerberg@linux.intel.com> (raw)
Hi,
This series includes a couple of fixes for issues found. I'm planning to
get these into v6.3-rc.
The first one is a memory leak fix.
The second one is fixing a reboot time issue reported by Christian that
we finally were able to reproduce in the lab. The reason this happened
only in Linux is that we enumerate retimers during link bring up and
there is certain step missing after the enumeration that leads the link
to not come up properly after soft-reboot. This should be fixed with
issuing UNSET_INBOUND_SBTX after retimer access and this works in the
lab.
@Christian, can you check that it solves the issue for you too?
The third one is a quirk that is needed for Intel hardware to limit the
USB3 bandwidth accordingly.
Gil Fine (2):
thunderbolt: Add missing UNSET_INBOUND_SBTX for retimer access
thunderbolt: Limit USB3 bandwidth of certain Intel USB4 host routers
Mika Westerberg (3):
thunderbolt: Fix memory leak in margining
thunderbolt: Call tb_check_quirks() after initializing adapters
thunderbolt: Use scale field when allocating USB3 bandwidth
drivers/thunderbolt/debugfs.c | 12 ++++----
drivers/thunderbolt/quirks.c | 31 ++++++++++++++++++++
drivers/thunderbolt/retimer.c | 23 +++++++++++++--
drivers/thunderbolt/sb_regs.h | 1 +
drivers/thunderbolt/switch.c | 4 +--
drivers/thunderbolt/tb.h | 4 +++
drivers/thunderbolt/usb4.c | 53 ++++++++++++++++++++++++++++++-----
7 files changed, 111 insertions(+), 17 deletions(-)
--
2.39.1
next reply other threads:[~2023-03-06 11:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 11:36 Mika Westerberg [this message]
2023-03-06 11:36 ` [PATCH 1/5] thunderbolt: Fix memory leak in margining Mika Westerberg
2023-03-06 11:36 ` [PATCH 2/5] thunderbolt: Add missing UNSET_INBOUND_SBTX for retimer access Mika Westerberg
2023-03-06 11:36 ` [PATCH 3/5] thunderbolt: Call tb_check_quirks() after initializing adapters Mika Westerberg
2023-03-06 11:36 ` [PATCH 4/5] thunderbolt: Limit USB3 bandwidth of certain Intel USB4 host routers Mika Westerberg
2023-03-06 11:36 ` [PATCH 5/5] thunderbolt: Use scale field when allocating USB3 bandwidth Mika Westerberg
2023-03-06 15:12 ` Yehezkel Bernat
2023-03-13 10:07 ` [PATCH 0/5] thunderbolt: A couple of fixes Mika Westerberg
2023-03-13 13:07 ` Christian Schaubschläger
2023-03-14 7:32 ` 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=20230306113605.46137-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=christian.schaubschlaeger@gmx.at \
--cc=gil.fine@linux.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 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).