public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Oliver Neukum <oliver@neukum.org>, Pavel Machek <pavel@suse.cz>,
	David Liontooth <liontooth@cogweb.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] USB devices fail unnecessarily on unpowered hubs
Date: Mon, 5 Jun 2006 07:32:52 -0700	[thread overview]
Message-ID: <200606050732.53496.david-b@pacbell.net> (raw)
In-Reply-To: <200606031129.54580.oliver@neukum.org>

On Saturday 03 June 2006 2:29 am, Oliver Neukum wrote:
> Am Dienstag, 30. Mai 2006 22:01 schrieb Pavel Machek:

> > Actually I have exactly opposite problem: my computer (spitz) can't
> > supply full 500mA on its root hub, and linux tries to power up
> > 'hungry' devices, anyway, leading to very weird behaviour.
> 
> 
> You could lower the obvious values in this code from drivers/usb/core/hub.c
> 
> 	if (hdev == hdev->bus->root_hub) {
> 		if (hdev->bus_mA == 0 || hdev->bus_mA >= 500)
> 			hub->mA_per_port = 500;
> 		else {
> 			hub->mA_per_port = hdev->bus_mA;
> 			hub->limited_power = 1;
> 		}
> 
> If that does the job we need to somehow inherit the power supply maximum from
> PCI when we allocate the root hub's device structure.

I don't think there is such a convention that's generic for PCI.  There might
be ACPI-specific tables holding that value, but on embedded hardware the model
is often that the arch/.../board-ZZZ.c file just "knows" things like how much
power the regulator powering that port can provide, and arranges bus_mA to match.
Just like it knows all sorts of other details about how that board works.

- Dave

  reply	other threads:[~2006-06-05 14:56 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01  9:18 USB devices fail unnecessarily on unpowered hubs David Liontooth
2006-05-30 20:01 ` Pavel Machek
2006-06-03  9:29   ` Oliver Neukum
2006-06-05 14:32     ` David Brownell [this message]
2006-06-06  7:43       ` [linux-usb-devel] " Oliver Neukum
2006-06-08  7:01         ` Pavel Machek
2006-06-08  8:34       ` [PATCH] limit power budget on spitz Pavel Machek
2006-06-08  8:50         ` Richard Purdie
2006-06-08  9:02           ` Pavel Machek
2006-06-08  9:22             ` Richard Purdie
2006-06-08 17:09               ` Russell King
2006-06-08 18:26                 ` David Brownell
2006-06-08 20:06                   ` Richard Purdie
2006-06-08 20:38                     ` [linux-usb-devel] " David Brownell
2006-06-08 21:22                       ` Richard Purdie
2006-06-08 21:40                         ` David Brownell
2006-06-08 21:49                           ` Richard Purdie
2006-06-08 23:44                             ` David Brownell
2006-06-09  1:25                               ` Nicolas Pitre
2006-06-09  2:03                                 ` David Brownell
2006-06-09  2:34                                   ` Nicolas Pitre
2006-06-01 10:01 ` USB devices fail unnecessarily on unpowered hubs Andrew Morton
2006-06-01 11:42   ` Daniel Drake
2006-06-01 14:58   ` Alan Stern
2006-06-01 15:09     ` linux-os (Dick Johnson)
2006-06-01 15:23       ` Lennart Sorensen
2006-06-01 21:39         ` Dagfinn Ilmari Mannsåker
2006-06-01 15:53       ` Oliver Neukum
2006-06-01 17:24         ` linux-os (Dick Johnson)
2006-06-01 16:57       ` Alan Stern
2006-06-01 16:43     ` [linux-usb-devel] " Greg KH
2006-06-02  0:03       ` David Liontooth
2006-06-02  1:53         ` [linux-usb-devel] " David Brownell
2006-06-02  7:12         ` Oliver Neukum
2006-06-02 15:11         ` Alan Stern
2006-06-02 19:49           ` David Liontooth
2006-06-01 16:59     ` Andrew Morton
2006-06-01 17:08       ` Alan Stern
2006-06-01 17:34   ` Mark Lord
2006-06-01 17:47     ` 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=200606050732.53496.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=liontooth@cogweb.net \
    --cc=oliver@neukum.org \
    --cc=pavel@suse.cz \
    /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