public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Richard Purdie <rpurdie@rpsys.net>, Pavel Machek <pavel@suse.cz>,
	lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>,
	linux-usb-devel@lists.sourceforge.net,
	Oliver Neukum <oliver@neukum.org>,
	David Liontooth <liontooth@cogweb.net>
Subject: Re: [PATCH] limit power budget on spitz
Date: Thu, 8 Jun 2006 11:26:18 -0700	[thread overview]
Message-ID: <200606081126.20142.david-b@pacbell.net> (raw)
In-Reply-To: <20060608170913.GB15337@flint.arm.linux.org.uk>

On Thursday 08 June 2006 10:09 am, Russell King wrote:
> On Thu, Jun 08, 2006 at 10:22:50AM +0100, Richard Purdie wrote:
> > Hi,
> > 
> > On Thu, 2006-06-08 at 11:02 +0200, Pavel Machek wrote:
> > > > > +	if (machine_is_spitz()) {
> > > > > +		/* Warning, not coming from any official docs. But
> > > > > +		 * spitz is unable to properly power wireless card
> > > > > +		 * claiming 500mA -- usb interface work but wireless
> > > > > +		 * does not. */
> > > > > +		hcd->power_budget = 250;
> > > > > +	}
> > > >
> > > > 
> > > > Should this value not be specified by the platform in the platform data
> > > > rather than a set of machine_is_xxx statements in the driver itself? I
> > > > already put most of the infrastructure for that into place.
> > > 
> > > Well, it has quite few users now, and this is how it works in
> > > ohci-omap. Yes, if we get more of such hooks, it probably needs to be
> > > moved to platform data...
> > 
> > Just because the omap does it that way, doesn't mean it can't be done
> > better ;-).

Agreed that platform_data is a better approach overall for holding that
power budget.  OMAP and AT91 should do so too.


> > I've also just realised the above doesn't account for akita 
> > or borzoi. Since the hardware is identical in this area, the same
> > changes should be applied for those machines. If we use the platform
> > device/data approach, we don't have this problem as they all use the
> > same platform device :)
> 
> So what do folk want me to do?  Blindly merge the patch (hint: it's still
> in the incoming queue...)

Sounds like someone should update the patch to (a) use a 150 mA budget,
and (b) test for those other machines.  As a near term patch, anyway.

Unless there's a patch to provide and use platform_data ... but that'd
be much more involved, since ISTR the PXA platforms don't yet have a
mechanism to provide board-specific platform_data.  (I'll suggest the
AT91 code as a model there; it's simpler hardware than OMAP, so the
code is more straightforward.)

- Dave



  reply	other threads:[~2006-06-08 18:26 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     ` [linux-usb-devel] " David Brownell
2006-06-06  7:43       ` 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 [this message]
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=200606081126.20142.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=lenz@cs.wisc.edu \
    --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 \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=rpurdie@rpsys.net \
    /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