From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] ARM: dts: twl: Add GPADC data to device tree
Date: Tue, 16 Jul 2013 18:22:08 +0400 [thread overview]
Message-ID: <51E55710.8060907@cogentembedded.com> (raw)
In-Reply-To: <1373974500-23609-1-git-send-email-oleksandr.kozaruk@ti.com>
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 <oleksandr.kozaruk@ti.com>
> ---
> 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
next prev parent reply other threads:[~2013-07-16 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 11:34 [PATCH v4 1/2] ARM: dts: twl: Add GPADC data to device tree Oleksandr Kozaruk
2013-07-16 11:35 ` [PATCH v4 2/2] iio: twl6030-gpadc: TWL6030, TWL6032 GPADC driver Oleksandr Kozaruk
2013-07-16 14:22 ` Sergei Shtylyov [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-16 11:47 [PATCH v4 0/2] " Oleksandr Kozaruk
2013-07-16 11:47 ` [PATCH v4 1/2] ARM: dts: twl: Add GPADC data to device tree Oleksandr Kozaruk
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=51E55710.8060907@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).