Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751158Ab3G0JQk (ORCPT ); Sat, 27 Jul 2013 05:16:40 -0400 Received: from mail-ve0-f176.google.com ([209.85.128.176]:60374 "EHLO mail-ve0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751042Ab3G0JQf (ORCPT ); Sat, 27 Jul 2013 05:16:35 -0400 MIME-Version: 1.0 In-Reply-To: References: <20130725175702.GC22291@e106331-lin.cambridge.arm.com> <51F168FC.9070906@wwwdotorg.org> <20130725182920.GA24955@e106331-lin.cambridge.arm.com> <20130725184834.GA8296@netboy> <20130725213753.GC17616@obsidianresearch.com> <20130726080115.GA5436@netboy> <1374831744.2923.42.camel@shinybook.infradead.org> <20130726130927.GC4219@netboy> <20130726132709.GH29916@titan.lakedaemon.net> <1374846070.14574.92.camel@i7.infradead.org> Date: Sat, 27 Jul 2013 17:16:34 +0800 Message-ID: Subject: Re: [Ksummit-2013-discuss] DT bindings as ABI [was: Do we have people interested in device tree janitoring / cleanup?] From: Ming Lei To: "jonsmirl@gmail.com" Cc: David Woodhouse , Jason Cooper , Mark Rutland , "devicetree@vger.kernel.org" , "ksummit-2013-discuss@lists.linuxfoundation.org" , Russell King - ARM Linux , Ian Campbell , Pawel Moll , Stephen Warren , Richard Cochran , Domenico Andreoli , "rob.herring@calxeda.com" , "linux-kernel@vger.kernel.org" , Jason Gunthorpe , Dave P Martin , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1201 Lines: 30 On Fri, Jul 26, 2013 at 10:14 PM, jonsmirl@gmail.com wrote: > > Yes, yes - that's why the schema should be written down and used as a > validation input to dtc. Then dtc can spit out errors for non-standard > items. There would be two versions - the standard one and a legacy one > that includes the standard one plus the hacks that can't be undone. > > But more importantly it provides a framework for people creating new > node definitions. Now they can't work in a vacuum and come up with > random names and structure for everything. > > Most of the problems express in the thread would go away if the schema > was written down and discussed. The rule going forward would be no new > nodes that aren't part of the standard schema. +1. If we want to keep the schema stable, it has to be defined and described explicitly with one language, just like syscall ABI: C type/API exported to userspace header file. Thanks, -- Ming Lei -- 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/