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>
Subject: Re: [PATCH 00/12] thunderbolt: Improve DisplayPort tunneling
Date: Fri, 3 Jan 2025 11:56:10 +0200 [thread overview]
Message-ID: <20250103095610.GQ3713119@black.fi.intel.com> (raw)
In-Reply-To: <20241217082222.528602-1-mika.westerberg@linux.intel.com>
On Tue, Dec 17, 2024 at 10:22:10AM +0200, Mika Westerberg wrote:
> Hi all,
>
> This series provides cleanups and few improvements for DisplayPort
> tunneling. First of all we increase the DPRX capabilites read timeout to
> cope with the fact that graphics driver may be runtime suspended. Secondly
> we move the DPRX negotiation to happen in a separate worker to allow
> forward progress even if the graphics driver is not yet loaded (this is
> kind if rare case but common in Intel Graphics CI).
>
> Mika Westerberg (12):
> thunderbolt: Drop doubled empty line from ctl.h
> thunderbolt: Log config space when invalid config space reply is received
> thunderbolt: Debug log an invalid config space reply just once
> thunderbolt: Increase DPRX capabilities read timeout
> thunderbolt: Make tb_tunnel_one_dp() return void
> thunderbolt: Show path name in debug log when path is deactivated
> thunderbolt: Rework how tunnel->[init|deinit] hooks are called
> thunderbolt: Drop tb_tunnel_restart()
> thunderbolt: Pass reason to tb_dp_resource_unavailable()
> thunderbolt: Move forward declarations in one place
> thunderbolt: Rework tb_tunnel_consumed_bandwidth()
> thunderbolt: Handle DisplayPort tunnel activation asynchronously
Applied to thunderbolt.git/next.
prev parent reply other threads:[~2025-01-03 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 8:22 [PATCH 00/12] thunderbolt: Improve DisplayPort tunneling Mika Westerberg
2024-12-17 8:22 ` [PATCH 01/12] thunderbolt: Drop doubled empty line from ctl.h Mika Westerberg
2024-12-17 8:22 ` [PATCH 02/12] thunderbolt: Log config space when invalid config space reply is received Mika Westerberg
2024-12-17 8:22 ` [PATCH 03/12] thunderbolt: Debug log an invalid config space reply just once Mika Westerberg
2024-12-17 8:22 ` [PATCH 04/12] thunderbolt: Increase DPRX capabilities read timeout Mika Westerberg
2024-12-17 8:22 ` [PATCH 05/12] thunderbolt: Make tb_tunnel_one_dp() return void Mika Westerberg
2024-12-17 8:22 ` [PATCH 06/12] thunderbolt: Show path name in debug log when path is deactivated Mika Westerberg
2024-12-17 8:22 ` [PATCH 07/12] thunderbolt: Rework how tunnel->[init|deinit] hooks are called Mika Westerberg
2024-12-17 8:22 ` [PATCH 08/12] thunderbolt: Drop tb_tunnel_restart() Mika Westerberg
2024-12-17 8:22 ` [PATCH 09/12] thunderbolt: Pass reason to tb_dp_resource_unavailable() Mika Westerberg
2024-12-17 8:22 ` [PATCH 10/12] thunderbolt: Move forward declarations in one place Mika Westerberg
2024-12-17 8:22 ` [PATCH 11/12] thunderbolt: Rework tb_tunnel_consumed_bandwidth() Mika Westerberg
2024-12-17 8:22 ` [PATCH 12/12] thunderbolt: Handle DisplayPort tunnel activation asynchronously Mika Westerberg
2024-12-19 17:03 ` Lukas Wunner
2024-12-19 17:29 ` Mika Westerberg
2025-01-03 9:56 ` Mika Westerberg [this message]
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=20250103095610.GQ3713119@black.fi.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