Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751856Ab1CKQx3 (ORCPT ); Fri, 11 Mar 2011 11:53:29 -0500 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:40726 "EHLO opensource2.wolfsonmicro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750893Ab1CKQx2 (ORCPT ); Fri, 11 Mar 2011 11:53:28 -0500 Date: Fri, 11 Mar 2011 16:53:26 +0000 From: Mark Brown To: Alan Stern Cc: andy.green@linaro.org, Arnd Bergmann , Linux USB list , lkml Subject: Re: RFC: Platform data for onboard USB assets Message-ID: <20110311165325.GU1760@opensource.wolfsonmicro.com> References: <4D7A4D52.6010501@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Cookie: You will contract a rare disease. User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 822 Lines: 16 On Fri, Mar 11, 2011 at 11:45:20AM -0500, Alan Stern wrote: > Or to put it another way... With external, hot-plugged USB devices, > there is no need to know "how it is wired". The fact that it is on a > USB bus is the only information necessary. Why does anyone need to > know more than this for on-board USB devices? Examples I'm aware of include things like power control beyond what the USB spec does and not programming device identification or configuration information that would normally be initialised by the hardware, relying on the AP to program it at runtime. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/