From: Matthias Kaehlcke <matthias.list@kaehlcke.net>
To: Samuel Ortiz <sameo@linux.intel.com>,
"AnilKumar, Chimata" <anilkumar@ti.com>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>
Cc: devicetree-discuss@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [RESEND] Documentation of device tree bindings for mfd devices
Date: Mon, 3 Sep 2012 18:19:06 +0200 [thread overview]
Message-ID: <20120903161906.GA23844@darwin> (raw)
Hi,
I wrote a driver for the backlight of the tps65217 PMIC, which is a
mfd device. The driver has device tree support and I want to document
the bindings.
It is not clear to me where this documentation should go. Currently
the bindings of the tps65217 driver are documented in
Documentation/devicetree/bindings/regulator/tps65217.txt , which
definitely isn't the right place to add backlight specific
documentation. The common practice seems to be to document mfd devices
including their subdevices in Documentation/devicetree/bindings/mfd.
To follow this convention my steps would be moving tps65217.txt to the
mfd directory and adding the backlight specific documentation.
Please confirm whether this is the correct/preferred way to document
device tree bindings of mfd devices
--
Matthias Kaehlcke
Embedded Linux Developer
Amsterdam
You can chain me, you can torture me, you can even
destroy this body, but you will never imprison my mind
(Mahatma Gandhi)
.''`.
using free software / Debian GNU/Linux | http://debian.org : :' :
`. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
reply other threads:[~2012-09-03 16:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120903161906.GA23844@darwin \
--to=matthias.list@kaehlcke.net \
--cc=anilkumar@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=sameo@linux.intel.com \
/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).