[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170217215611.2ft4rpnukbijcgqn@localhost>
Date: Fri, 17 Feb 2017 22:56:11 +0100
From: Rask Ingemann Lambertsen <rask@...melder.dk>
To: Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc: Emil Velikov <emil.l.velikov@...il.com>,
Mark Rutland <mark.rutland@....com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
devicetree <devicetree@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
ML dri-devel <dri-devel@...ts.freedesktop.org>,
linux-mm@...ck.org, Tobias Jakobi <tjakobi@...h.uni-bielefeld.de>,
Chen-Yu Tsai <wens@...e.org>, Rob Herring <robh+dt@...nel.org>,
LAKML <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements
On Fri, Feb 17, 2017 at 04:44:19PM +0100, Maxime Ripard wrote:
[...]
> We already have DT bindings for out of tree drivers, there's really
> nothing new here.
We have DT bindings for *hardware*, not for drivers. As stated in
Documentation/devicetree/usage-model.txt:
"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."
"2.1 High Level View
-------------------
The most important thing to understand is that the DT is simply a data
structure that describes the hardware."
--
Rask Ingemann Lambertsen
Powered by blists - more mailing lists