| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 26 Jan 2010 07:21:28 -0800 From: David Brownell <david-b@...bell.net> To: felipe.balbi@...ia.com Cc: Mark Brown <broonie@...nsource.wolfsonmicro.com>, "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Anton Vorontsov <avorontsov@...mvista.com>, Grazvydas Ignotas <notasas@...il.com>, Madhusudhan Chikkature <madhu.cr@...com>, "linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>, "Greg Kroah-Hartman" <gregkh@...e.de> Subject: Re: [RFC/PATCH 1/5] usb: otg: add notifier support On Tuesday 26 January 2010, Felipe Balbi wrote: > > > >Thing is, supplying current is a bit more involved. If the > >board can't supply 300 mA, the USB configuration selection > >mechanism has to know that, so it never selects peripheral > >configurations which require that much current. > > but that's done already by the usb core, no ? It rules out configuration > based on the hub->power_budget (can't remember if the field is that > exact name). Yes, it handles that ... but where does the power budget come from? That's what I meant by "more involved". As in, the host/supplying side of the power equation can't be event driven like the peripheral/consuming side can. And that's another reason I think it's best to fully solve the common (peripheral, recharge-that-batter) case first. - Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists