From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-la0-f48.google.com ([209.85.215.48]:51862 "EHLO mail-la0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754721Ab3GPOWJ (ORCPT ); Tue, 16 Jul 2013 10:22:09 -0400 Received: by mail-la0-f48.google.com with SMTP id lx15so571122lab.7 for ; Tue, 16 Jul 2013 07:22:07 -0700 (PDT) Message-ID: <51E55710.8060907@cogentembedded.com> Date: Tue, 16 Jul 2013 18:22:08 +0400 From: Sergei Shtylyov MIME-Version: 1.0 To: Oleksandr Kozaruk CC: tony@atomide.com, benoit.cousson@linaro.org, rnayak@ti.com, peter.ujfalusi@ti.com, kishon@ti.com, jic23@cam.ac.uk, grant.likely@linaro.org, rob.herring@calxeda.com, lars@metafoo.de, sameo@linux.intel.com, ch.naveen@samsung.com, poeschel@lemonage.de, milo.kim@ti.com, balajitk@ti.com, gg@slimlogic.co.uk, linux-iio@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v4 1/2] ARM: dts: twl: Add GPADC data to device tree References: <1373974500-23609-1-git-send-email-oleksandr.kozaruk@ti.com> In-Reply-To: <1373974500-23609-1-git-send-email-oleksandr.kozaruk@ti.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: linux-iio-owner@vger.kernel.org List-Id: linux-iio@vger.kernel.org Hello. On 07/16/2013 03:34 PM, Oleksandr Kozaruk wrote: > GPADC is the general purpose ADC present on twl6030. > The dt data is interrupt used to trigger end of ADC > conversion. > Signed-off-by: Oleksandr Kozaruk > --- > arch/arm/boot/dts/twl6030.dtsi | 6 ++++++ > 1 file changed, 6 insertions(+) > diff --git a/arch/arm/boot/dts/twl6030.dtsi b/arch/arm/boot/dts/twl6030.dtsi > index 2e3bd31..434842c 100644 > --- a/arch/arm/boot/dts/twl6030.dtsi > +++ b/arch/arm/boot/dts/twl6030.dtsi > @@ -103,4 +103,10 @@ > compatible = "ti,twl6030-pwmled"; > #pwm-cells = <2>; > }; > + > + gpadc: twl6030_gpadc { > + compatible = "ti,twl6030_gpadc"; > + interrupts = <3>; > + #io-channel-cells = <1>; > + }; ePAPR [1] says: "The name of a node should be somewhat generic, reflecting the function of the device and not its precise programming model." [1] http://www.power.org/resources/downloads/Power_ePAPR_APPROVED_v1.0.pdf WBR, Sergei