[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20120903161906.GA23844@darwin>
Date: Mon, 3 Sep 2012 18:19:06 +0200
From: Matthias Kaehlcke <matthias.list@...hlcke.net>
To: Samuel Ortiz <sameo@...ux.intel.com>,
"AnilKumar, Chimata" <anilkumar@...com>,
Grant Likely <grant.likely@...retlab.ca>,
Rob Herring <rob.herring@...xeda.com>
Cc: devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: [RESEND] Documentation of device tree bindings for mfd devices
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 `-
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists