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

Linus Walleij linus.walleij at linaro.org
Mon Jul 15 08:36:22 UTC 2013

On Sun, Jul 14, 2013 at 8:13 PM, Guenter Roeck <linux at roeck-us.net> wrote:
> On Sun, Jul 14, 2013 at 01:46:45AM +0200, Linus Walleij wrote:>> Maybe some just consider this "some documentation", think it has been
>> defined by someone who thought it over and merge it without looking
>> closely.
> For my part I do have a close look, but I don't really know if my understanding
> of acceptable properties matches the understanding of the devicetree community.
> Devicetree is supposed to describe the hardware, but in many cases there is
> an overlap between hardware description and configuration and/or use. Where is
> the boundary ?

Well this is what we need everyone to know so I guess this confirms the
need to bring it up at the kernel summit...

> My approach is to accept properties which would otherwise require platform data.
> Is that acceptable ?

In most cases yes, but there are some paradigms about it, and nothing
linux-specific should be encoded in it, except for a few "linux-*"

> How can I know if devicetree-discuss is mostly silent on
> such matters, as you point out ?

Right now it feels like everyone developing these drivers think it is very
convenient that the Linux subsystem maintainers do all the reviewing
and deciding, so they can then later take the blame for it if they merged
something bad.

I feel just as ambivalent about it as you do :-/

Linus Walleij

More information about the Ksummit-2013-discuss mailing list