From: "Patil, Rachna" <rachna@ti.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Dmitry Torokhov <dtor@mail.ru>,
Rob Herring <rob.herring@calxeda.com>,
Jonathan Cameron <jic23@cam.ac.uk>,
Tony Lindgren <tony@atomide.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Landley <rob@landley.net>,
Russell King <linux@arm.linux.org.uk>
Subject: RE: [PATCH v3 4/8] MFD: ti_am335x_tscadc: add device tree binding information
Date: Tue, 22 Jan 2013 09:31:02 +0000 [thread overview]
Message-ID: <4CE347531D4CA947960AF71FF095B9323E9AFB02@DBDE01.ent.ti.com> (raw)
In-Reply-To: <50FB1DFE.6090805@metafoo.de>
Hi,
On Sun, Jan 20, 2013 at 03:58:14, Lars-Peter Clausen wrote:
> Hi,
>
> On 01/18/2013 11:48 AM, Patil, Rachna wrote:
> > From: "Patil, Rachna" <rachna@ti.com>
> >
> > Signed-off-by: Patil, Rachna <rachna@ti.com>
> > ---
> > .../devicetree/bindings/mfd/ti_am335x_tscadc.txt | 35 ++++++++++++++++++++
> > 1 file changed, 35 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/mfd/ti_am335x_tscadc.txt
> >
> > diff --git
> > a/Documentation/devicetree/bindings/mfd/ti_am335x_tscadc.txt
> > b/Documentation/devicetree/bindings/mfd/ti_am335x_tscadc.txt
> > new file mode 100644
> > index 0000000..c13c492
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/mfd/ti_am335x_tscadc.txt
> > @@ -0,0 +1,35 @@
> > +Texas Instruments - TSC / ADC multi-functional device
> > +
> > +ti_tscadc is a multi-function device with touchscreen and ADC on chip.
> > +This document describes the binding for mfd device.
> > +
> > +Required properties:
> > +- compatible: "ti,ti-tscadc"
> > +- reg: Specifies the address of MFD block
> > +- interrupts: IRQ line connected to the main SoC
> > +- interrupt-parent: The parent interrupt controller
>
> The subnodes and their properties also need documentation.
Ok. I Will add this.
>
> > +
> > +Optional properties:
> > +- ti,hwmods: Hardware information related to TSC/ADC MFD device
> > +
> > +Example:
> > +
> > + tscadc: tscadc@44e0d000 {
> > + compatible = "ti,ti-tscadc";
> > + reg = <0x44e0d000 0x1000>;
> > +
> > + interrupt-parent = <&intc>;
> > + interrupts = <16>;
> > + ti,hwmods = "adc_tsc";
> > +
> > + tsc {
> > + wires = <4>;
> > + x-plate-resistance = <200>;
> > + steps-to-configure = <5>;
> > + wire-config = <0x00 0x11 0x22 0x33>;
>
> Non-standard properties should have a vendor prefix.
Ok. I will fix this in the next version of the patch set.
Regards,
Rachna
next prev parent reply other threads:[~2013-01-22 9:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 10:44 [PATCH v3 0/8] MFD: ti_am335x_tscadc: DT support and TSC features addition Patil, Rachna
2013-01-18 10:47 ` [PATCH v3 1/8] input: ti_am335x_tsc: Step enable bits made configurable Patil, Rachna
2013-01-18 10:47 ` [PATCH v3 2/8] input: ti_am335x_tsc: Order of TSC wires, " Patil, Rachna
2013-01-18 10:48 ` [PATCH v3 3/8] input: touchscreen: ti_tsc: remove unwanted fifo flush Patil, Rachna
2013-01-27 13:55 ` Peter Korsgaard
2013-01-18 10:48 ` [PATCH v3 4/8] MFD: ti_am335x_tscadc: add device tree binding information Patil, Rachna
2013-01-19 22:28 ` Lars-Peter Clausen
2013-01-22 9:31 ` Patil, Rachna [this message]
2013-01-18 10:48 ` [PATCH v3 5/8] MFD: ti_am335x_tscadc: Add DT support Patil, Rachna
2013-01-18 10:48 ` [PATCH v3 6/8] input: ti_am335x_tsc: " Patil, Rachna
2013-01-18 10:48 ` [PATCH v3 7/8] IIO: ti_am335x_adc: " Patil, Rachna
2013-01-18 10:48 ` [PATCH v3 8/8] arm/dts: AM335x-evm: Add TSC/ADC MFD device support Patil, Rachna
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=4CE347531D4CA947960AF71FF095B9323E9AFB02@DBDE01.ent.ti.com \
--to=rachna@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@mail.ru \
--cc=grant.likely@secretlab.ca \
--cc=jic23@cam.ac.uk \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sameo@linux.intel.com \
--cc=tony@atomide.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).