public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: Not enough bandwidth for new device state -- with Etron USB3 controller only
Date: Thu, 22 Apr 2021 16:08:13 +0500	[thread overview]
Message-ID: <20210422160813.41e26426@natsu> (raw)
In-Reply-To: <YIEOcvePnzGlQtoy@kroah.com>

Hello,

On Thu, 22 Apr 2021 07:49:38 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:

> Not a bug, this is how USB works.  Your first hub really does not have
> enough bandwidth for that device.  Well, we think it doesn't, the
> calculation for that is really really tricky and we error on the side of
> "let's not take the risk and just disable the device to be safe".
> 
> Get a better hub :)

But why the calculation is different when the hub is plugged into the onboard
USB 2.0 controller -- and there it works?

I hope you don't take this as a bug report to make it stop working there as
well. :)

If it's because the Etron controller is USB 3.0, and the higher speeds are
somehow accounted for in the bandwidth calculation, that doesn't seem right,
since both of the plugged in downstream hubs are 1.1/2.0-only.

-- 
With respect,
Roman

  reply	other threads:[~2021-04-22 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 17:37 Not enough bandwidth for new device state -- with Etron USB3 controller only Roman Mamedov
2021-04-22  5:49 ` Greg KH
2021-04-22 11:08   ` Roman Mamedov [this message]
2021-04-22 11:15     ` Greg KH
2021-04-22 14:21       ` Alan Stern

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=20210422160813.41e26426@natsu \
    --to=rm@romanrm.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    /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