devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [RESEND] Documentation of device tree bindings for mfd devices
@ 2012-09-03 16:19 Matthias Kaehlcke
  0 siblings, 0 replies; only message in thread
From: Matthias Kaehlcke @ 2012-09-03 16:19 UTC (permalink / raw)
  To: Samuel Ortiz, AnilKumar, Chimata, Grant Likely, Rob Herring
  Cc: devicetree-discuss, linux-kernel

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                  `-

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2012-09-03 16:19 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-09-03 16:19 [RESEND] Documentation of device tree bindings for mfd devices Matthias Kaehlcke

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).