From: rask@formelder.dk (Rask Ingemann Lambertsen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] ARM: sun8i: a33: Mali improvements
Date: Fri, 17 Feb 2017 22:56:11 +0100 [thread overview]
Message-ID: <20170217215611.2ft4rpnukbijcgqn@localhost> (raw)
In-Reply-To: <20170217154419.xr4n2ikp4li3c7co@lukather>
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
next prev parent reply other threads:[~2017-02-17 21:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <10fd28cb-269a-ec38-ecfb-b7c86be3e716@math.uni-bielefeld.de>
2017-02-16 16:54 ` [PATCH 0/8] ARM: sun8i: a33: Mali improvements Emil Velikov
2017-02-17 15:44 ` Maxime Ripard
2017-02-17 20:39 ` Emil Velikov
2017-02-24 0:19 ` Maxime Ripard
2017-02-26 12:14 ` Emil Velikov
2017-02-17 21:56 ` Rask Ingemann Lambertsen [this message]
2017-02-16 18:45 ` Maxime Ripard
2017-02-17 12:45 ` Tobias Jakobi
2017-02-17 13:20 ` Emil Velikov
2017-02-17 15:42 ` Alexandre Belloni
2017-02-17 15:56 ` Tobias Jakobi
2017-02-24 13:56 ` Rob Herring
2017-02-17 15:43 ` Maxime Ripard
2017-02-20 16:49 ` Thierry Reding
2017-02-23 0:44 ` Maxime Ripard
2017-02-09 16:39 Maxime Ripard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170217215611.2ft4rpnukbijcgqn@localhost \
--to=rask@formelder.dk \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox