From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
nicolas.ferre@atmel.com, alexandre.belloni@free-electrons.com,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, galak@codeaurora.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v7 2/2] PWM: atmel-pwm: add device tree binding document
Date: Fri, 15 Nov 2013 14:44:00 +0100 [thread overview]
Message-ID: <20131115134400.GN28304@ns203013.ovh.net> (raw)
In-Reply-To: <1384509208-10762-2-git-send-email-voice.shen@atmel.com>
On 17:53 Fri 15 Nov , Bo Shen wrote:
> Add atmel pwm driver device tree binding document
>
> Signed-off-by: Bo Shen <voice.shen@atmel.com>
> Acked-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> Acked-by: Kumar Gala <galak@codeaurora.org>
Acked-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Best Regards,
J.
> ---
> Changes in v7: None
> Changes in v6:
> - New, split binding document as a separate patch
>
> Changes in v5: None
> Changes in v4: None
> Changes in v3: None
> Changes in v2: None
>
> .../devicetree/bindings/pwm/atmel-pwm.txt | 41 ++++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pwm/atmel-pwm.txt
>
> diff --git a/Documentation/devicetree/bindings/pwm/atmel-pwm.txt b/Documentation/devicetree/bindings/pwm/atmel-pwm.txt
> new file mode 100644
> index 0000000..1c1a5fa
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pwm/atmel-pwm.txt
> @@ -0,0 +1,41 @@
> +Atmel PWM controller
> +
> +Required properties:
> + - compatible: should be one of:
> + - "atmel,at91sam9rl-pwm"
> + - "atmel,sama5d3-pwm"
> + - reg: physical base address and length of the controller's registers
> + - #pwm-cells: Should be 3. See pwm.txt in this directory for a
> + description of the cells format
> +
> +Example:
> +
> + pwm0: pwm@f8034000 {
> + compatible = "atmel,at91sam9rl-pwm";
> + reg = <0xf8034000 0x400>;
> + #pwm-cells = <3>;
> + };
> +
> +The following the pwm led based example:
> +
> + pwm0: pwm@f8034000 {
> + compatible = "atmel,at91sam9rl-pwm";
> + reg = <0xf8034000 0x400>;
> + #pwm-cells = <3>;
> + };
> +
> + pwdleds {
> + compatible = "pwm-leds";
> +
> + d1 {
> + label = "d1";
> + pwms = <&pwm0 3 5000 0>
> + max-brightness = <255>;
> + };
> +
> + d2 {
> + label = "d2";
> + pwms = <&pwm0 1 5000 1>
> + max-brightness = <255>;
> + };
> + };
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2013-11-15 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 9:53 [PATCH v7 1/2] PWM: atmel-pwm: add PWM controller driver Bo Shen
2013-11-15 9:53 ` [PATCH v7 2/2] PWM: atmel-pwm: add device tree binding document Bo Shen
2013-11-15 13:44 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2013-11-15 13:46 ` [PATCH v7 1/2] PWM: atmel-pwm: add PWM controller driver Jean-Christophe PLAGNIOL-VILLARD
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=20131115134400.GN28304@ns203013.ovh.net \
--to=plagnioj@jcrosoft.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=thierry.reding@gmail.com \
--cc=voice.shen@atmel.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).