All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Yehezkel Bernat <YehezkelShB@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Lukas Wunner <lukas@wunner.de>,
	Andreas Noever <andreas.noever@gmail.com>
Cc: Gil Fine <gil.fine@linux.intel.com>, linux-usb@vger.kernel.org
Subject: Re: [PATCH 1/2] thunderbolt: Fix calculation of consumed USB3 bandwidth on a path
Date: Fri, 12 Apr 2024 09:51:33 +0300	[thread overview]
Message-ID: <20240412065133.GD112498@black.fi.intel.com> (raw)
In-Reply-To: <20240408130031.51616-1-mika.westerberg@linux.intel.com>

On Mon, Apr 08, 2024 at 04:00:30PM +0300, Mika Westerberg wrote:
> From: Gil Fine <gil.fine@linux.intel.com>
> 
> Currently, when setup a new USB3 tunnel that is starting from downstream USB3
> adapter of first depth router (or deeper), to upstream USB3 adapter of a second
> depth router (or deeper), we calculate consumed bandwidth. For this calculation
> we take into account first USB3 tunnel consumed bandwidth while we shouldn't,
> because we just recalculating the first USB3 tunnel allocated bandwidth.
> 
> Fix that, so that more bandwidth is available for the new USB3 tunnel being
> setup.
> 
> While there, fix the kernel-doc to decribe more accurately the purpose of the
> function.
> 
> Signed-off-by: Gil Fine <gil.fine@linux.intel.com>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>

Both applied to thunderbolt.git/next.

      parent reply	other threads:[~2024-04-12  6:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 13:00 [PATCH 1/2] thunderbolt: Fix calculation of consumed USB3 bandwidth on a path Mika Westerberg
2024-04-08 13:00 ` [PATCH 2/2] thunderbolt: Allow USB3 bandwidth to be lower than maximum supported Mika Westerberg
2024-04-12  6:51 ` 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=20240412065133.GD112498@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.