From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org,
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>
Subject: Re: [PATCH 2/3] thunderbolt: Notify userspace about software CM tunneling events
Date: Thu, 10 Apr 2025 16:26:31 +0300 [thread overview]
Message-ID: <20250410132631.GX3152277@black.fi.intel.com> (raw)
In-Reply-To: <2025041001-baritone-flaccid-8306@gregkh>
On Thu, Apr 10, 2025 at 03:18:12PM +0200, Greg KH wrote:
> On Thu, Apr 10, 2025 at 04:13:50PM +0300, Mika Westerberg wrote:
> > On Thu, Apr 10, 2025 at 03:01:54PM +0200, Greg KH wrote:
> > > On Thu, Apr 10, 2025 at 03:55:59PM +0300, Mika Westerberg wrote:
> > > > From: Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>
> > > >
> > > > This adds notification whenever software connection manager activates,
> > > > changes or deactivates a tunnel, and also if there is limitation in
> > > > bandwidth.
> > > >
> > > > The notification looks like below:
> > > >
> > > > TUNNEL_EVENT=activated|changed|deactivated|low bandwidth|
> > > > insufficient bandwidth
> > > > TUNNEL_DETAILS=0:12 <-> 1:20 (USB3)
> > > >
> > > > Userspace can then listen these and inform user if needed. For example
> > > > if there is not enough bandwidth, it can show warning dialog to the user.
> > > >
> > > > Signed-off-by: Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>
> > >
> > > You didn't sign off on this? :(
> >
> > Oops, sorry missed it completely. I'll fix this in v2.
> >
> > > Also, you are adding a new user/kernel api here, where is it documented?
> >
> > Hm, where uevent documentation lives? I know for sysfs is under
> > Documentation/ABI/* but not sure for uevents.
>
> Maybe in your Documentation/admin-guide/thunderbolt.rst file?
Works for me. We'll add it there. Thanks!
next prev parent reply other threads:[~2025-04-10 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 12:55 [PATCH 0/3] thunderbolt: Notify userspace about tunneling events in the domain Mika Westerberg
2025-04-10 12:55 ` [PATCH 1/3] thunderbolt: Introduce domain event message handler Mika Westerberg
2025-04-10 12:55 ` [PATCH 2/3] thunderbolt: Notify userspace about software CM tunneling events Mika Westerberg
2025-04-10 13:01 ` Greg KH
2025-04-10 13:13 ` Mika Westerberg
2025-04-10 13:18 ` Greg KH
2025-04-10 13:26 ` Mika Westerberg [this message]
2025-04-10 12:56 ` [PATCH 3/3] thunderbolt: Notify userspace about firmware " 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=20250410132631.GX3152277@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