Linux USB
 help / color / mirror / Atom feed
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>,
	Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>,
	Saranya Gopal <saranya.gopal@intel.com>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 0/4] thunderbolt: Notify userspace about tunneling events in the domain
Date: Thu, 24 Apr 2025 08:36:15 +0300	[thread overview]
Message-ID: <20250424053615.GM88033@black.fi.intel.com> (raw)
In-Reply-To: <20250417090426.221773-1-mika.westerberg@linux.intel.com>

On Thu, Apr 17, 2025 at 12:04:22PM +0300, Mika Westerberg wrote:
> Hi all,
> 
> This series adds support to sending uevents to userspace about changes in
> tunneling such as creation, removal and bandwidth related.  One intented
> use-case for this is an upcoming USB-C daemon developed by Saranya that
> then notifies user for example if there is not enough bandwidth for
> DisplayPort requirements. We also added debug tools [1] support for these
> (currently it just updates various screens on event but we are working on
> add event log there too).
> 
> The Firmware Connection manager side is kind of limited though since there
> are not that many notifications we get.
> 
> [1] https://github.com/intel/tbtools
> 
> Previous version can be found:
> 
>   https://lore.kernel.org/linux-usb/20250410125600.3074417-1-mika.westerberg@linux.intel.com/
> 
> Changes from the previous version:
> 
>   * Add missing SoB.
>   * Add documentation to admin-guide/thunderbolt.rst.
> 
> Alan Borzeszkowski (4):
>   thunderbolt: Introduce domain event message handler
>   thunderbolt: Notify userspace about software CM tunneling events
>   thunderbolt: Notify userspace about firmware CM tunneling events
>   Documentation/admin-guide: Document Thunderbolt/USB4 tunneling events

Changed the documentation to say:

  "The format currently matches what the driver uses when logging. This may change over time."

and applied the whole series to thunderbolt.git/next.

      parent reply	other threads:[~2025-04-24  5:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17  9:04 [PATCH v2 0/4] thunderbolt: Notify userspace about tunneling events in the domain Mika Westerberg
2025-04-17  9:04 ` [PATCH v2 1/4] thunderbolt: Introduce domain event message handler Mika Westerberg
2025-04-17  9:04 ` [PATCH v2 2/4] thunderbolt: Notify userspace about software CM tunneling events Mika Westerberg
2025-04-17  9:04 ` [PATCH v2 3/4] thunderbolt: Notify userspace about firmware " Mika Westerberg
2025-04-17  9:04 ` [PATCH v2 4/4] Documentation/admin-guide: Document Thunderbolt/USB4 " Mika Westerberg
2025-04-17  9:39   ` Greg KH
2025-04-17 10:04     ` Mika Westerberg
2025-04-17 10:25       ` Greg KH
2025-04-17 10:33         ` Mika Westerberg
2025-04-17 10:41           ` Greg KH
2025-04-17 10:46             ` Mika Westerberg
2025-04-24  5:36 ` 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=20250424053615.GM88033@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=alan.borzeszkowski@linux.intel.com \
    --cc=andreas.noever@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=michael.jamet@intel.com \
    --cc=saranya.gopal@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