From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 2/5] Documentation: bindings: document the Berlin PWM driver
Date: Mon, 21 Sep 2015 10:14:39 +0200 [thread overview]
Message-ID: <20150921081439.GD19865@ulmo.nvidia.com> (raw)
In-Reply-To: <1442484788-15482-3-git-send-email-antoine.tenart@free-electrons.com>
On Thu, Sep 17, 2015 at 12:13:05PM +0200, Antoine Tenart wrote:
> Following the addition of a Berlin PWM driver, this patch adds the
> corresponding documentation.
>
> Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com>
> Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> ---
> Documentation/devicetree/bindings/pwm/pwm-berlin.txt | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pwm/pwm-berlin.txt
That's the wrong way around. You define the binding, get concensus that
it's okay and then implement the binding in the driver. Of course you'd
always provide both the binding and an implementation in the same patch
series for convenience, but that doesn't change the logical ordering.
> diff --git a/Documentation/devicetree/bindings/pwm/pwm-berlin.txt b/Documentation/devicetree/bindings/pwm/pwm-berlin.txt
> new file mode 100644
> index 000000000000..8f9bc11f8c4c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pwm/pwm-berlin.txt
> @@ -0,0 +1,19 @@
> +Berlin PWM controller
> +
> +PWM IP found in Marvell Berlin SoCs.
This isn't a proper sentence and doesn't add much useful information. If
you want to say anything here, provide details about the PWM controller.
> +
> +Required properties:
> +- compatible: should be "marvell,berlin-pwm"
> +- reg: physical base address and length of the controller's registers
> +- clocks: phandle to the input clock
You should think about adding a clock-names property here as well.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150921/3c1d9ad9/attachment.sig>
next prev parent reply other threads:[~2015-09-21 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 10:13 [PATCH v6 0/5] ARM: berlin: PWM support Antoine Tenart
2015-09-17 10:13 ` [PATCH v6 1/5] pwm: add the Berlin pwm controller driver Antoine Tenart
2015-09-20 18:13 ` Sebastian Hesselbarth
2015-09-21 8:09 ` Thierry Reding
2015-09-21 21:05 ` Sebastian Hesselbarth
2015-09-21 8:40 ` Thierry Reding
2015-09-25 9:15 ` Antoine Tenart
2015-09-17 10:13 ` [PATCH v6 2/5] Documentation: bindings: document the Berlin PWM driver Antoine Tenart
2015-09-21 8:14 ` Thierry Reding [this message]
2015-09-17 10:13 ` [PATCH v6 3/5] ARM: berlin: add a PWM node on the BG2Q Antoine Tenart
2015-09-17 10:13 ` [PATCH v6 4/5] ARM: berlin: add a PWM node on the BG2 Antoine Tenart
2015-09-17 10:13 ` [PATCH v6 5/5] ARM: berlin: add a PWM node on the BG2CD Antoine Tenart
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=20150921081439.GD19865@ulmo.nvidia.com \
--to=thierry.reding@gmail.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).