From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760188AbZE1Hjl (ORCPT ); Thu, 28 May 2009 03:39:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754331AbZE1Hje (ORCPT ); Thu, 28 May 2009 03:39:34 -0400 Received: from gate.crashing.org ([63.228.1.57]:51505 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751213AbZE1Hjd (ORCPT ); Thu, 28 May 2009 03:39:33 -0400 Subject: Re: [RFC] [PATCH] Device Tree on ARM platform From: Benjamin Herrenschmidt To: Russell King Cc: Scott Wood , devicetree-discuss , linux-kernel@vger.kernel.org, Timur Tabi , Janboe Ye , linux-arm-kernel@lists.arm.linux.org.uk In-Reply-To: <20090527175609.GB31861@flint.arm.linux.org.uk> References: <1243408083.13460.14.camel@debian-nb> <20090527150527.GK6805@pengutronix.de> <87vdnm8sec.fsf@macbook.be.48ers.dk> <4A1D6901.2090508@freescale.com> <20090527175609.GB31861@flint.arm.linux.org.uk> Content-Type: text/plain Date: Thu, 28 May 2009 17:37:16 +1000 Message-Id: <1243496236.3171.140.camel@pasglop> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2009-05-27 at 18:56 +0100, Russell King wrote: > > smc91x is a prime example of the kind of information drivers need - base > address and irq are very much insufficient to describe how this device is > connected. There's much more information required to specify this device > fully, and throwing it into the driver doesn't work. We've been there > and proven that point. The device-tree is a very nice and convenient way to convey all the informations the driver need straight to the driver without any platform code in the middle :-) Cheers, Ben. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [RFC] [PATCH] Device Tree on ARM platform Date: Thu, 28 May 2009 17:37:16 +1000 Message-ID: <1243496236.3171.140.camel@pasglop> References: <1243408083.13460.14.camel@debian-nb> <20090527150527.GK6805@pengutronix.de> <87vdnm8sec.fsf@macbook.be.48ers.dk> <4A1D6901.2090508@freescale.com> <20090527175609.GB31861@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090527175609.GB31861-f404yB8NqCZvn6HldHNs0ANdhmdF6hFW@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org To: Russell King Cc: devicetree-discuss , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Timur Tabi , Scott Wood , Janboe Ye , linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org List-Id: devicetree@vger.kernel.org On Wed, 2009-05-27 at 18:56 +0100, Russell King wrote: > > smc91x is a prime example of the kind of information drivers need - base > address and irq are very much insufficient to describe how this device is > connected. There's much more information required to specify this device > fully, and throwing it into the driver doesn't work. We've been there > and proven that point. The device-tree is a very nice and convenient way to convey all the informations the driver need straight to the driver without any platform code in the middle :-) Cheers, Ben.