linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: linux-usb@vger.kernel.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Greg Kroah-Hartman <gregkh@kernel.org>,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: Question about regulators
Date: Tue, 9 Apr 2019 09:26:34 +0200	[thread overview]
Message-ID: <20190409092634.222919dd@xps13> (raw)
In-Reply-To: <20190403101343.718c156d@xps13>

Hello,

Adding Greg & Hans just in case they have an idea, or someone else to
ping in mind.

Miquel Raynal <miquel.raynal@bootlin.com> wrote on Wed, 3 Apr 2019
10:13:43 +0200:

> Hello,
> 
> I am reading the document named "xHCI interoperability testing v0.94"
> available on usb.org. There is this paragraph:
> 
>         Devices operating at Enhanced SuperSpeed GenX are allowed to
>         draw a maximum configured current of 900mA and unconfigured
>         current of 150mA. Devices operating at High-Speed or below may
>         draw a maximum configured current of 500mA and unconfigured
>         current of 100mA*. Devices must report their maximum configured
>         current draw and their power configuration as self or bus
>         powered to the host and must operate within the regions
>         reported. Additionally any device that is in the suspended
>         state may draw no more than 2.5 mA.
> 
> My understanding is that the current limitation on Vbus should be tuned
> dynamically between 100, 150, 500 and 900mA depending on the type of
> device and if has been configured or not.
> 
> Despite some researches in the USB core I can't find any mechanism
> handling this in Linux implementation.
> 
> Behind this remark, I actually have boards (Armada 7040/8040 DB) with a
> regulator on Vbus to limit the current to either 500 or 900mA. I
> checked the xhci-platform driver which is used with these SoCs and I
> don't find any mean to tweak this value depending on the inserted
> device.
> 
> Should I actually care? Is it enough to limit to 900mA whenever the
> xHCI driver is probed?
> 
> Thanks for your guidance,
> Miquèl


Thanks,
Miquèl

       reply	other threads:[~2019-04-09  7:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190403101343.718c156d@xps13>
2019-04-09  7:26 ` Miquel Raynal [this message]
2019-04-09  7:38   ` Question about regulators Hans de Goede
2019-04-09  7:41     ` Miquel Raynal
2019-04-09 14:14       ` 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=20190409092634.222919dd@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=gregkh@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).