linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: "Kozaruk, Oleksandr" <oleksandr.kozaruk@ti.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
	"Kim, Milo" <Milo.Kim@ti.com>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"sameo@linux.intel.com" <sameo@linux.intel.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"tony@atomide.com" <tony@atomide.com>,
	"Nayak, Rajendra" <rnayak@ti.com>,
	"poeschel@lemonage.de" <poeschel@lemonage.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	"ABRAHAM, KISHON VIJAY" <kishon@ti.com>,
	"Ujfalusi, Peter" <peter.ujfalusi@ti.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"jic23@cam.ac.uk" <jic23@cam.ac.uk>,
	"grant.likely@linaro.org" <grant.likely@linaro.org>,
	"benoit.cousson@linaro.org" <benoit.cousson@linaro.org>,
	"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>,
	"ch.naveen@samsung.com" <ch.naveen@samsung.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Krishnamoorthy, Balaji T" <balajitk@ti.com>
Subject: Re: [PATCH v8 0/2] TWL6030, TWL6032 GPADC driver
Date: Fri, 16 Aug 2013 09:54:40 +0100	[thread overview]
Message-ID: <20130816085440.GF32421@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <2A7ABDFCE21540479A5AEB0244A684D5E3EE9C@DNCE04.ent.ti.com>

On Fri, Aug 16, 2013 at 07:39:35AM +0100, Kozaruk, Oleksandr wrote:
> >On 08/15/13 13:59, Mark Rutland wrote:
> >> On Thu, Aug 15, 2013 at 12:03:02PM +0100, Jonathan Cameron wrote:
> >>>
> >>>>> The changes to the original driver:
> >>>>> - device tree adaptation;
> >>>>
> >>>> I couldn't see a binding document in this series or in mainline. Have I
> >>>> looked in the wrong places?
> >>>
> >>> Nothing explicit supplied, but does it need one given it is doing only
> >>> iio bindings (bindings/iio/iio-bindings.txt)
> >>> plus twl child bindings
> >>> (bindings/mfd/twl-family.txt)
> >>
> >> Every binding needs to be documented.
> >>
> >>>
> >>> If it does, I guess absolutely everything does, then fair enough!
> >>> I guess that would make sense as there is no way for someone writing
> >>> a device tree to know that there is nothing else to be specified.
> >>
> >> Yup, that's why. Also, Linux isn't necessarily the only consumer, and
> >> other consumers shouldn't need to read Linux code to figure out how a
> >> particular binding is supposed to look.
> >>
> >Fair enough. Thanks for clearing that up.
> >
> >Oleksandr, could you send a follow up patch adding the required documentation?
> >(mostly a cut and paste job from similar elements by the look of it).
> >
> 
> Hello,
> 
> Is this good enough?
> 
> From 211e81ff4a146d9ec27443696a429e795c58dc30 Mon Sep 17 00:00:00 2001
> From: Oleksandr Kozaruk <oleksandr.kozaruk@ti.com>
> Date: Thu, 15 Aug 2013 16:14:11 +0300
> Subject: [PATCH] iio: adc: Add bindigs documentation for twl6030 GPADC
> 
> Add required documentation for twl6030 GPADC device tree
> bindings.
> 
> Signed-off-by: Oleksandr Kozaruk <oleksandr.kozaruk@ti.com>
> ---
>  .../devicetree/bindings/iio/adc/twl6030-gpadc.txt          | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/iio/adc/twl6030-gpadc.txt
> 
> diff --git a/Documentation/devicetree/bindings/iio/adc/twl6030-gpadc.txt b/Documentation/devicetree/bindings/iio/adc/twl6030-gpadc.txt
> new file mode 100644
> index 0000000..6829420
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/twl6030-gpadc.txt
> @@ -0,0 +1,14 @@
> +Texas Instruments twl6030/twl6032 GPADC device driver
> +
> +Required properties:
> +       - compatible: must be "ti,twl6030-gpadc" for TWL6030 or
> +         "ti,twl6032-gpadc" for TWL6032
> +       - interrupts: interrupt number associated with it
> +       - #io-channel-cells: must be <1> - multiple IIO outputs

There should be a desscription of valid values for the io-channel-cells
as used by consumers.

Otherwise, this looks fine.

Thanks,
Mark.

> +
> +Example:
> +       adc {
> +               compatible = "ti,twl6030-gpadc";
> +               interrupts = <3>;
> +               #io-channel-cells = <1>;
> +       };
> 
> -- 
> 1.8.1.2
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

  reply	other threads:[~2013-08-16  8:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 13:26 [PATCH v8 0/2] TWL6030, TWL6032 GPADC driver Oleksandr Kozaruk
2013-07-25 13:26 ` [PATCH v8 1/2] ARM: dts: twl: Add GPADC data to device tree Oleksandr Kozaruk
2013-07-25 13:26 ` [PATCH v8 2/2] iio: twl6030-gpadc: TWL6030, TWL6032 GPADC driver Oleksandr Kozaruk
2013-08-14 22:09   ` Jonathan Cameron
2013-08-15  5:45     ` Oleksandr Kozaruk
2013-08-15  9:31       ` Jonathan Cameron
2013-08-19 10:26         ` Oleksandr Kozaruk
2013-08-15  9:12 ` [PATCH v8 0/2] " Mark Rutland
     [not found]   ` <520CB566.2050201@kernel.org>
2013-08-15 12:59     ` Mark Rutland
     [not found]       ` <520D16EC.90604@kernel.org>
2013-08-16  6:39         ` Kozaruk, Oleksandr
2013-08-16  8:54           ` Mark Rutland [this message]
2013-08-16 12:48             ` Kozaruk, Oleksandr

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=20130816085440.GF32421@e106331-lin.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --cc=Milo.Kim@ti.com \
    --cc=balajitk@ti.com \
    --cc=benoit.cousson@linaro.org \
    --cc=ch.naveen@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gg@slimlogic.co.uk \
    --cc=grant.likely@linaro.org \
    --cc=jic23@cam.ac.uk \
    --cc=jic23@kernel.org \
    --cc=kishon@ti.com \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=oleksandr.kozaruk@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=poeschel@lemonage.de \
    --cc=rnayak@ti.com \
    --cc=rob.herring@calxeda.com \
    --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).