Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933370Ab3GWPzR (ORCPT ); Tue, 23 Jul 2013 11:55:17 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:52164 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932138Ab3GWPzO (ORCPT ); Tue, 23 Jul 2013 11:55:14 -0400 Message-ID: <51EEA75E.3050008@wwwdotorg.org> Date: Tue, 23 Jul 2013 08:55:10 -0700 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: Tomasz Figa CC: Jon Loeliger , "Chaiken, Alison" , Grant Likely , Wolfram Sang , Mark Rutland , Ian Campbell , Pawel Moll , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Rob Herring , Olof Johansson , Mark Brown , Linus Walleij Subject: Re: The future of DT binding maintainership References: <1925583.R0td2pS6as@flatron> <1687020.5ErE9ecltl@flatron> In-Reply-To: <1687020.5ErE9ecltl@flatron> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1560 Lines: 30 On 07/22/2013 02:57 PM, Tomasz Figa wrote: > On Monday 22 of July 2013 16:34:49 Jon Loeliger wrote: >>> My idea is to implement compile time verification in dtc, so I guess it >>> will be more like the latter. Since dts is what dtc can already parse, >>> my plan is to keep the schemas in spirit to dts, just >>> modifying/extending it to allow specifying bindings with them, rather >>> than static values. > Things start to become fun when you get to bindings like regulators or > clocks, when part of the binding is defined on generic level (-supply, > clocks, clock-names properties) and remaining part is specific to device > (XXX in XXX-supply, count and order of clocks and clock-names, strings > allowed in clock-names property). This kind of inheritance is likely to be > the biggest troublemaker. It's good you mentioned inheritance here. I believe that's one of the key things. For example, the Tegra GPIO controller's binding is-a GPIO-controller, and is-an interrupt-controller, and I imagine any successful DT schema definition would very explicitly include that information. Likewise, other nodes may be is-a GPIO-client (many times, each parameterized with the property name that defines which GPIO you're talking abot), and also may be is-an interrupt-client (with a similar comment), etc. -- 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/