Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932337Ab1CVVJO (ORCPT ); Tue, 22 Mar 2011 17:09:14 -0400 Received: from gate.crashing.org ([63.228.1.57]:43750 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932230Ab1CVVJM (ORCPT ); Tue, 22 Mar 2011 17:09:12 -0400 Subject: Re: RFC: Platform data for onboard USB assets From: Benjamin Herrenschmidt To: Jaswinder Singh Cc: andy.green@linaro.org, Andy Green , Linux USB list , lkml , arnd@arndb.de, broonie@opensource.wolfsonmicro.com, roger.quadros@nokia.com, greg@kroah.com, grant.likely@secretlab.ca, Nicolas Pitre In-Reply-To: References: <4D79F068.2080009@linaro.org> Content-Type: text/plain; charset="UTF-8" Date: Wed, 23 Mar 2011 08:08:45 +1100 Message-ID: <1300828125.2402.300.camel@pasglop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 908 Lines: 24 > Q(b) If yes, what 'key' is most suitable for identifying the right > device > to attach the data to ? We already pointed out that in the case of soldered-in device, the "path" as in the series of -physical- ports leading to the device is going to be stable. For anything else, there's no solution. If the device doesn't have a unique ID, you are toast, period. On the other hand, I still think platform_data suck big time. Grant made some good points about the lack of proper typing for example. I believe that a device-tree based approach is much better in the long run (and more flexible) despite Andy odd quasi-religious aversion for it. Cheers, Ben. -- 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/