From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [Ksummit-2013-discuss] [RFC] of: Allow for experimental device tree bindings
Date: Thu, 24 Oct 2013 23:29:33 +0100 [thread overview]
Message-ID: <52699F4D.7030805@wwwdotorg.org> (raw)
In-Reply-To: <20131024083459.48FE3C4039D@trevor.secretlab.ca>
On 10/24/2013 09:34 AM, Grant Likely wrote:
> On Wed, 23 Oct 2013 18:20:02 +0100, Wolfram Sang <wsa@the-dreams•de> wrote:
>>
>>> Do we really want to polute the drivers and DT files with a ! in the
>>> compatible values? I thought we'd considered that, but chosen having the
>>> drivers that use unstable bindings depend on a Kconfig option as an
>>> alternative, not an additional step?
>>
>> I'd even go further and use "unstable-" as the prefix instead of "!"
>> which is way more explicit.
>>
>>
>>> The one issue with doing this is that if a binding is thought to be
>>> unstable, but becomes stable later without any changes, we'll have to do
>>> busy-work to remove the ! in all the DT files, thus artificially
>>> introducing an incompatibility. Perhaps that's fine though?
>>
>> I'd say yes. Going from unstable to stable is quite a step for a binding
>> and that should be visible and worth a patch IMO. Also, when looking at
>> a DTS file or some driver code, it will avoid
>> confusion/misinterpretation if one can see immediately the status of a
>> binding.
>
> No, it shouldn't. Going from unstable to stable is not a large step, rather it is coming to the point of looking around and realizing that the binding is working quite well.
>
> I don't think the solution is to put this into the kernel to be checked
> at runtime. The better solution is to put it into DTC and make it
> complain (either warn or error; depending on build config?) about usage
> of compatible strings that are marked in the binding documentation as
> unstable.
I don't think that's what we talked about on Wednesday though. At a
quick glance, this didn't make it into the meeting notes though[1], but
is in the presentation we created for the kernel summit readout. Is
sharing a link to that before it's presented OK?
[1] http://etherpad.osuosl.org/arm-ksummit-2013-day-2
next prev parent reply other threads:[~2013-10-24 22:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 15:06 [RFC] of: Allow for experimental device tree bindings Thierry Reding
2013-10-23 16:05 ` [Ksummit-2013-discuss] " David Woodhouse
2013-10-23 16:55 ` Guenter Roeck
2013-10-23 17:05 ` David Woodhouse
2013-10-23 18:56 ` Thierry Reding
2013-10-23 18:51 ` Thierry Reding
2013-10-24 22:26 ` Stephen Warren
2013-10-25 8:22 ` Thierry Reding
2013-10-25 8:45 ` Stephen Warren
2013-10-23 16:33 ` Stephen Warren
2013-10-23 17:20 ` [Ksummit-2013-discuss] " Wolfram Sang
2013-10-23 18:59 ` Thierry Reding
2013-10-23 19:34 ` Jason Gunthorpe
2013-10-23 19:58 ` Thierry Reding
2013-10-23 21:08 ` Jason Gunthorpe
2013-10-24 8:04 ` Thierry Reding
2013-10-24 17:32 ` Jason Gunthorpe
2013-10-23 21:13 ` Andy Lutomirski
2013-10-23 19:40 ` Wolfram Sang
2013-10-23 20:05 ` Thierry Reding
2013-10-24 8:34 ` Grant Likely
2013-10-24 8:50 ` Thierry Reding
2013-10-24 20:26 ` Matt Sealey
2013-10-24 22:29 ` Stephen Warren [this message]
2013-10-24 18:39 ` jonsmirl at gmail.com
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=52699F4D.7030805@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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