From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: RFC: Platform data for onboard USB assets Date: Sat, 19 Mar 2011 09:47:09 +1100 Message-ID: <1300488429.22236.1291.camel@pasglop> References: <20110311165642.GA9996@kroah.com> <201103181600.09877.arnd@arndb.de> <4D839BCD.6030202@linaro.org> <201103182106.13888.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201103182106.13888.arnd-r2nGTMty4D4@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: Arnd Bergmann Cc: Nicolas Pitre , andy.green-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, Greg KH , devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org, Mark Brown , lkml , Linux USB list List-Id: devicetree@vger.kernel.org On Fri, 2011-03-18 at 21:06 +0100, Arnd Bergmann wrote: > > In a perfect world, we would need neither the device tree nor > any platform data at all, because we'd be able to ask the hardware > or the fictionary correct firmware about what the properties > of the hardware are. This works to a surprisingly large extent > on server hardware, but much less so on typical embedded systems. Properties of the HW per-se but also binding information, ie, what is connected to what outside of the main bus path (think clock/power control etc...). Even server / desktop is affected here, and nobody sane thinks ACPI is a -good- solution here tho it works mostly on x86 :-) Cheers, Ben.