Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

From: Maxime Ripard
Date: Thu Feb 23 2017 - 19:21:50 EST


On Fri, Feb 17, 2017 at 08:39:33PM +0000, Emil Velikov wrote:
> As I feared things have taken a turn for the bitter end :-]
> It seems that this is a heated topic, so I'l kindly ask that we try
> the following:
> - For people such as myself/Tobias/others who feel that driver and DT
> bindings should go hand in hand, prove them wrong.
> But please, do so by pointing to the documentation (conclusion of a
> previous discussion). This way you don't have to repeat yourself and
> get [too] annoyed over silly suggestions.

"The "Open Firmware Device Tree", or simply Device Tree (DT), is a
data structure and language for describing hardware. More
specifically, it is a description of hardware that is readable by an
operating system so that the operating system doesn't need to hard
code details of the machine"

"What it does do is provide a language for decoupling the hardware
configuration from the board and device driver support in the Linux
kernel (or any other operating system for that matter)."

And like I said, we already had bindings for out of tree bindings,
like this one:

Which triggered no discussion at the time (but the technical one,
hence a v2, that should always be done).

> - The series has code changes which [seemingly] cater for out of tree
> module(s).

That patch was dropped, only DT changes remains now, and do not depend
of that missing patch anyway.

> Clearly state in the commit message who is the user, why it's save to
> do so and get an Ack from more prominent [DRM] developers.

DRM is really not important here. We could implement a driver using
i2c as far as the DT is concerned.

FreeBSD for example uses a different, !DRM framework to support our
display stack, and still uses the DT.


Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering

Attachment: signature.asc
Description: PGP signature