Re: [Ksummit-2013-discuss] [ATTEND] Handling of devicetree bindings

[Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>]

On Mon, 15 Jul 2013 19:50:27 +0100, David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> wrote:
> On Mon, 2013-07-15 at 09:56 -0700, Greg KH wrote:
> > How about a hint for subsystem maintainers as to what exactly we should
> > be looking for with these bindings?  I for one have no idea what is
> > "right" vs. "wrong" with them, so a document explaining this would be
> > good to have.
> > 
> > Or if we already have it, a pointer to it perhaps?
> 
> The biggest thing is that it should describe the *hardware*, in a
> fashion which is completely OS-agnostic.
> 
> The same device-tree binding should work for Solaris, *BSD, Windows,
> eCos, and everything else.
> 
> I've heard tales of people having to keep device-tree files for their
> board tightly in sync with the specific *version* of the Linux kernel
> that they were shipped with.
> 
> That makes me very sad, because it almost certainly means that someone
> has done it completely and utterly wrong.

It is wrong, but it has happened. At first it was getting up and running
with DT in ARM which was a major shift, but now it is down to lack of
process. There is a new team of maintainers for DT bindings that I've
just sent and email about. The ultimate goal is to add schema checking
to device tree bindings and get them out of the kernel entirely. That
should resolve the tightly-coupled problem that we're currently dealing
with.

g.