From: Ben Gamari <bgamari.foss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Subject: Re: [PATCH] dt: Update I2C trivial devices list
Date: Mon, 13 Jan 2014 12:26:47 -0500 [thread overview]
Message-ID: <87ob3flrmw.fsf@gmail.com> (raw)
In-Reply-To: <52D41B14.6060701-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> writes:
> On 01/13/2014 07:25 AM, Ben Gamari wrote:
>> Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org> writes:
>>> What about putting this into a seperate paragraph prefixed with "Current
>>> Linux specific implementation:"?
>>>
>> This would address my concern quite nicely.
>
> The text should go into Documentation/ not the DT binding.
>
The problem here is that as it stands DT is quite daunting to pick
up. My needs are pretty minimal yet I had to spend many hours sifting
through source, blogs, and Documentation/* to get something that more or
less worked. The bindings are generally well-documented, but there is no
"start here" document in the tree giving conventions and an overview of
how Linux in particular uses DT.
The closest thing I know of is Documentation/devicetree/usage-model.txt.
Perhaps this is where the language Wolfram suggested should be placed.
Cheers,
- Ben
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2014-01-13 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 0:12 [PATCH] dt: Update I2C trivial devices list Ben Gamari
[not found] ` <1387239151-19226-1-git-send-email-bgamari.foss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-17 16:14 ` Stephen Warren
[not found] ` <52B07870.6070809-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-12-17 16:47 ` Ben Gamari
[not found] ` <87a9fztofc.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-01-13 12:51 ` Wolfram Sang
2014-01-13 14:25 ` Ben Gamari
[not found] ` <87r48cklgj.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-01-13 16:57 ` Stephen Warren
[not found] ` <52D41B14.6060701-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-01-13 17:26 ` Ben Gamari [this message]
[not found] ` <87ob3flrmw.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-19 14:24 ` Wolfram Sang
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=87ob3flrmw.fsf@gmail.com \
--to=bgamari.foss-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@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).