From: Timur Tabi <timur-N01EOCouUvQ@public.gmane.org>
To: Sebastian Frias <sf84-QFKgK+z4sOrR7s880joybQ@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Cc: devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Mason <slash.tmp-GANU6spQydw@public.gmane.org>,
Linux ARM
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: ARM, SoC: About the use DT-defined properties by 3rd-party drivers
Date: Tue, 13 Sep 2016 06:37:16 -0500 [thread overview]
Message-ID: <57D7E4EC.6050509@tabi.org> (raw)
In-Reply-To: <57D7CF17.2050905-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
Sebastian Frias wrote:
> Let's make an abstraction of the word 'binding', 'create a binding', etc. and
> just focus on this:
> - Somebody submits a DT file that contains properties and nodes that are
> *not used* by any Linux driver.
> - Said properties and nodes serve as HW description for HW blocks for which
> *there is no* Linux driver.
>
> The goal of the above is to use the DT as the authoritative (and single)
> source of HW definition.
No.
I've grown weary of this discussion. We have explained multiple times
why this is impractical. Using the DT to document hardware makes no
sense. No one is going to do that, and anyone who attempts to submit a
DT binding without an actual driver will get rejected.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-09-13 11:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 14:29 ARM,SoC: About the use DT-defined properties by 3rd-party drivers Sebastian Frias
2016-08-28 20:36 ` ARM, SoC: " Timur Tabi
2016-09-12 12:29 ` ARM,SoC: " Sebastian Frias
[not found] ` <57D69FB1.2020801-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2016-09-12 12:38 ` Mark Rutland
2016-09-12 13:15 ` Sebastian Frias
2016-09-12 13:23 ` Timur Tabi
2016-09-12 14:01 ` ARM, SoC: " Mark Rutland
2016-09-12 14:26 ` Warner Losh
2016-09-12 16:29 ` Sebastian Frias
2016-09-12 16:45 ` Warner Losh
2016-09-12 16:49 ` Timur Tabi
2016-09-12 17:07 ` Mark Rutland
2016-09-12 17:06 ` Mark Rutland
2016-09-12 16:07 ` Sebastian Frias
[not found] ` <57D6D2A9.3010006-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2016-09-12 16:21 ` Timur Tabi
2016-09-12 16:26 ` Sebastian Frias
2016-09-12 16:56 ` Mark Rutland
2016-09-13 10:04 ` Sebastian Frias
[not found] ` <57D7CF17.2050905-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2016-09-13 11:37 ` Timur Tabi [this message]
[not found] ` <57D7E4EC.6050509-N01EOCouUvQ@public.gmane.org>
2016-09-13 13:23 ` Mark Rutland
2016-09-13 13:12 ` Mark Rutland
2016-09-13 14:22 ` Sebastian Frias
[not found] ` <57D80B91.4020306-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2016-09-13 14:51 ` Mark Rutland
2016-09-14 8:32 ` Sebastian Frias
2016-09-13 14:55 ` Sebastian Frias
[not found] ` <57D8137F.8040508-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2016-09-13 15:47 ` Mark Rutland
2016-09-14 8:24 ` Sebastian Frias
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=57D7E4EC.6050509@tabi.org \
--to=timur-n01eocouuvq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=sf84-QFKgK+z4sOrR7s880joybQ@public.gmane.org \
--cc=slash.tmp-GANU6spQydw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).