From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM, SoC: About the use DT-defined properties by 3rd-party drivers
Date: Tue, 13 Sep 2016 16:47:30 +0100 [thread overview]
Message-ID: <20160913154722.GD23336@leverpostej> (raw)
In-Reply-To: <57D8137F.8040508@laposte.net>
On Tue, Sep 13, 2016 at 04:55:59PM +0200, Sebastian Frias wrote:
> On 09/13/2016 03:12 PM, Mark Rutland wrote:
> >> Exactly, that is why I was thinking it would take less "review" time.
> >> Indeed, if there is no driver, why would it matter what those bindings
> >> are?
> >
> > If you believe that the bindings don't matter, then there is absolutely
> > no reason for them to exist in the first place.
> >
> > If those binding matter to *anyone*, then those collating the bindings
> > have some responsibility of stewardship, and that includes
> > review/maintenance/etc.
>
> The thing is that right now it seems the "responsibility of stewardship"
> lies only within "Linux", whereas DT is proposed as open for everybody,
> Bootloaders, FreeBSD, etc.
>
> In that case, shouldn't the "responsibility" be shared?
Ideally, yes.
Which is one of the reasons devicetree.org was set up as a common forum
for projects to collaborate on devicetree.
Thanks,
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Sebastian Frias <sf84-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
Cc: devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Mason <slash.tmp-GANU6spQydw@public.gmane.org>,
Timur Tabi <timur-N01EOCouUvQ@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 16:47:30 +0100 [thread overview]
Message-ID: <20160913154722.GD23336@leverpostej> (raw)
In-Reply-To: <57D8137F.8040508-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
On Tue, Sep 13, 2016 at 04:55:59PM +0200, Sebastian Frias wrote:
> On 09/13/2016 03:12 PM, Mark Rutland wrote:
> >> Exactly, that is why I was thinking it would take less "review" time.
> >> Indeed, if there is no driver, why would it matter what those bindings
> >> are?
> >
> > If you believe that the bindings don't matter, then there is absolutely
> > no reason for them to exist in the first place.
> >
> > If those binding matter to *anyone*, then those collating the bindings
> > have some responsibility of stewardship, and that includes
> > review/maintenance/etc.
>
> The thing is that right now it seems the "responsibility of stewardship"
> lies only within "Linux", whereas DT is proposed as open for everybody,
> Bootloaders, FreeBSD, etc.
>
> In that case, shouldn't the "responsibility" be shared?
Ideally, yes.
Which is one of the reasons devicetree.org was set up as a common forum
for projects to collaborate on devicetree.
Thanks,
Mark.
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Sebastian Frias <sf84@laposte.net>
Cc: devicetree <devicetree@vger.kernel.org>,
Mason <slash.tmp@free.fr>, Timur Tabi <timur@tabi.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ARM, SoC: About the use DT-defined properties by 3rd-party drivers
Date: Tue, 13 Sep 2016 16:47:30 +0100 [thread overview]
Message-ID: <20160913154722.GD23336@leverpostej> (raw)
In-Reply-To: <57D8137F.8040508@laposte.net>
On Tue, Sep 13, 2016 at 04:55:59PM +0200, Sebastian Frias wrote:
> On 09/13/2016 03:12 PM, Mark Rutland wrote:
> >> Exactly, that is why I was thinking it would take less "review" time.
> >> Indeed, if there is no driver, why would it matter what those bindings
> >> are?
> >
> > If you believe that the bindings don't matter, then there is absolutely
> > no reason for them to exist in the first place.
> >
> > If those binding matter to *anyone*, then those collating the bindings
> > have some responsibility of stewardship, and that includes
> > review/maintenance/etc.
>
> The thing is that right now it seems the "responsibility of stewardship"
> lies only within "Linux", whereas DT is proposed as open for everybody,
> Bootloaders, FreeBSD, etc.
>
> In that case, shouldn't the "responsibility" be shared?
Ideally, yes.
Which is one of the reasons devicetree.org was set up as a common forum
for projects to collaborate on devicetree.
Thanks,
Mark.
next prev parent reply other threads:[~2016-09-13 15:47 UTC|newest]
Thread overview: 71+ 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-24 14:29 ` Sebastian Frias
2016-08-28 20:36 ` ARM, SoC: " Timur Tabi
2016-08-28 20:36 ` ARM,SoC: " Timur Tabi
2016-08-28 20:36 ` ARM, SoC: " Timur Tabi
2016-09-12 12:29 ` Sebastian Frias
2016-09-12 12:29 ` ARM,SoC: " Sebastian Frias
2016-09-12 12:38 ` ARM, SoC: " Mark Rutland
2016-09-12 12:38 ` ARM,SoC: " Mark Rutland
2016-09-12 12:38 ` Mark Rutland
2016-09-12 13:15 ` ARM, SoC: " Sebastian Frias
2016-09-12 13:15 ` ARM,SoC: " Sebastian Frias
2016-09-12 13:23 ` ARM, SoC: " Timur Tabi
2016-09-12 13:23 ` ARM,SoC: " Timur Tabi
2016-09-12 14:01 ` ARM, SoC: " Mark Rutland
2016-09-12 14:01 ` Mark Rutland
2016-09-12 14:26 ` Warner Losh
2016-09-12 14:26 ` Warner Losh
2016-09-12 14:26 ` Warner Losh
2016-09-12 16:29 ` Sebastian Frias
2016-09-12 16:29 ` Sebastian Frias
2016-09-12 16:45 ` Warner Losh
2016-09-12 16:45 ` Warner Losh
2016-09-12 16:49 ` Timur Tabi
2016-09-12 16:49 ` Timur Tabi
2016-09-12 17:07 ` Mark Rutland
2016-09-12 17:07 ` Mark Rutland
2016-09-12 17:06 ` Mark Rutland
2016-09-12 17:06 ` Mark Rutland
2016-09-12 17:06 ` Mark Rutland
2016-09-12 16:07 ` Sebastian Frias
2016-09-12 16:07 ` Sebastian Frias
2016-09-12 16:07 ` Sebastian Frias
2016-09-12 16:21 ` Timur Tabi
2016-09-12 16:21 ` Timur Tabi
2016-09-12 16:21 ` Timur Tabi
2016-09-12 16:26 ` Sebastian Frias
2016-09-12 16:26 ` Sebastian Frias
2016-09-12 16:26 ` Sebastian Frias
2016-09-12 16:56 ` Mark Rutland
2016-09-12 16:56 ` Mark Rutland
2016-09-12 16:56 ` Mark Rutland
2016-09-13 10:04 ` Sebastian Frias
2016-09-13 10:04 ` Sebastian Frias
2016-09-13 10:04 ` Sebastian Frias
2016-09-13 11:37 ` Timur Tabi
2016-09-13 11:37 ` Timur Tabi
2016-09-13 11:37 ` Timur Tabi
2016-09-13 13:23 ` Mark Rutland
2016-09-13 13:23 ` Mark Rutland
2016-09-13 13:23 ` Mark Rutland
2016-09-13 13:12 ` Mark Rutland
2016-09-13 13:12 ` Mark Rutland
2016-09-13 13:12 ` Mark Rutland
2016-09-13 14:22 ` Sebastian Frias
2016-09-13 14:22 ` Sebastian Frias
2016-09-13 14:22 ` Sebastian Frias
2016-09-13 14:51 ` Mark Rutland
2016-09-13 14:51 ` Mark Rutland
2016-09-13 14:51 ` Mark Rutland
2016-09-14 8:32 ` Sebastian Frias
2016-09-14 8:32 ` Sebastian Frias
2016-09-14 8:32 ` Sebastian Frias
2016-09-13 14:55 ` Sebastian Frias
2016-09-13 14:55 ` Sebastian Frias
2016-09-13 14:55 ` Sebastian Frias
2016-09-13 15:47 ` Mark Rutland [this message]
2016-09-13 15:47 ` Mark Rutland
2016-09-13 15:47 ` Mark Rutland
2016-09-14 8:24 ` Sebastian Frias
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=20160913154722.GD23336@leverpostej \
--to=mark.rutland@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.