From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Daniel Drake <dsd-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
dilinger-pFFUokh25LWsTnJN9+BGXg@public.gmane.org
Subject: Re: [RFC 3/3] olpc-battery: bind to device tree
Date: Mon, 14 Mar 2011 21:32:03 -0600 [thread overview]
Message-ID: <20110315033203.GB5600@angua.secretlab.ca> (raw)
In-Reply-To: <AANLkTik-bXgiAtLsB4rRS2oo-xToLjHkNkNy=FV11UA5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Sat, Mar 12, 2011 at 05:56:12PM +0000, Daniel Drake wrote:
> On 5 March 2011 04:54, Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:
> > I want to see all new compatible properties documented in
> > Documentation/devicetree/bindings. It may not be the best place for
> > binding documentation since it is currently tied to Linux, but it is
> > better than anything else we currently have.
>
> Ok, how do you think it should look?
>
> Something simple like this? new file at bindings/power_supply/olpc_battery.txt :
>
> OLPC battery
> ~~~~~~~~~~~~
>
> Required properties:
> - compatible : "olpc,xo1-battery"
Yes. At the very least it captures the usage of a compatible
property. Eventually I'm going to translate this stuff into a cross
referenced online database.
prev parent reply other threads:[~2011-03-15 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 17:12 [RFC 3/3] olpc-battery: bind to device tree Daniel Drake
[not found] ` <20110304171241.0DCF89D401E-k/4jFdqg8LLlyo9zxV8I99HuzzzSOjJt@public.gmane.org>
2011-03-04 18:23 ` Andres Salomon
2011-03-05 4:54 ` Grant Likely
[not found] ` <20110305045440.GI7579-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2011-03-12 17:56 ` Daniel Drake
[not found] ` <AANLkTik-bXgiAtLsB4rRS2oo-xToLjHkNkNy=FV11UA5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-15 3:32 ` Grant Likely [this message]
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=20110315033203.GB5600@angua.secretlab.ca \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=dilinger-pFFUokh25LWsTnJN9+BGXg@public.gmane.org \
--cc=dsd-2X9k7bc8m7Mdnm+yROfE0A@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