From: Matt Porter <matt.porter@linaro.org>
To: Grant Likely <grant.likely@linaro.org>
Cc: Xiubo Li <Li.Xiubo@freescale.com>,
r65073@freescale.com, thierry.reding@gmail.com,
mark.rutland@arm.com, linux-pwm@vger.kernel.org,
linux@arm.linux.org.uk, ian.campbell@citrix.com,
pawel.moll@arm.com, swarren@wwwdotorg.org,
s.hauer@pengutronix.de, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rob.herring@calxeda.com,
devicetree@vger.kernel.org, rob@landley.net, t.figa@samsung.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv5 4/4] Documentation: Add device tree bindings for Freescale FTM PWM.
Date: Sat, 26 Oct 2013 09:02:25 -0400 [thread overview]
Message-ID: <20131026130225.GJ29341@beef> (raw)
In-Reply-To: <20131025201211.7936EC405D3@trevor.secretlab.ca>
On Fri, Oct 25, 2013 at 09:12:11PM +0100, Grant Likely wrote:
> On Mon, 30 Sep 2013 14:13:31 +0800, Xiubo Li <Li.Xiubo@freescale.com> wrote:
> > This adds the Document for Freescale FTM PWM driver under
> > Documentation/devicetree/bindings/pwm/.
> >
> > Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
> > ---
> > .../devicetree/bindings/pwm/pwm-fsl-ftm.txt | 33 ++++++++++++++++++++++
> > 1 file changed, 33 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt
> >
> > diff --git a/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt b/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt
> > new file mode 100644
> > index 0000000..2c6969a
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt
> > @@ -0,0 +1,33 @@
> > +Freescale FTM PWM controller
> > +
> > +Required properties:
> > +- compatible: Should be "fsl,vf610-ftm-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.
> > +- clock-names : Includes the following module clock source entries:
> > + "ftm0" (system clock),
> > + "ftm0_fix_sel" (fixed frequency clock),
> > + "ftm0_ext_sel" (external clock)
> > +- clocks : Must contain a clock specifier for each entry in clock-names.
> > +- fsl,pwm-counter-clk: The FTM PWM counter clock source, should be one of the
> > + entries in clock-names.
> > +- pinctrl-names: must contain a "default" entry.
> > +- pinctrl-NNN: One property must exist for each entry in pinctrl-names.
> > + See ../pinctrl/pinctrl-bindings.txt for details of the property values.
>
> Looks okay to me.
For consistency, shouldn't it also have:
"See ../clock/clock-bindings.txt for details of the property values"
where appropriate like is done under the pwm/pinctrl uses?
IMHO, referencing parent bindings all of the time should be a documented
best practice / requirement.
-Matt
> > +
> > +
> > +Example:
> > +
> > +pwm0: pwm@40038000 {
> > + compatible = "fsl,vf610-ftm-pwm";
> > + reg = <0x40038000 0x1000>;
> > + #pwm-cells = <3>;
> > + clock-names = "ftm0", "ftm0_fix_sel", "ftm0_ext_sel";
> > + clocks = <&clks VF610_CLK_FTM0>,
> > + <&clks VF610_CLK_FTM0_FIX_SEL>,
> > + <&clks VF610_CLK_FTM0_EXT_SEL>;
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pinctrl_pwm0_1>;
> > + fsl,pwm-counter-clk = "ftm0_ext_sel";
> > +};
> > --
> > 1.8.0
> >
> >
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: matt.porter@linaro.org (Matt Porter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5 4/4] Documentation: Add device tree bindings for Freescale FTM PWM.
Date: Sat, 26 Oct 2013 09:02:25 -0400 [thread overview]
Message-ID: <20131026130225.GJ29341@beef> (raw)
In-Reply-To: <20131025201211.7936EC405D3@trevor.secretlab.ca>
On Fri, Oct 25, 2013 at 09:12:11PM +0100, Grant Likely wrote:
> On Mon, 30 Sep 2013 14:13:31 +0800, Xiubo Li <Li.Xiubo@freescale.com> wrote:
> > This adds the Document for Freescale FTM PWM driver under
> > Documentation/devicetree/bindings/pwm/.
> >
> > Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
> > ---
> > .../devicetree/bindings/pwm/pwm-fsl-ftm.txt | 33 ++++++++++++++++++++++
> > 1 file changed, 33 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt
> >
> > diff --git a/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt b/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt
> > new file mode 100644
> > index 0000000..2c6969a
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt
> > @@ -0,0 +1,33 @@
> > +Freescale FTM PWM controller
> > +
> > +Required properties:
> > +- compatible: Should be "fsl,vf610-ftm-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.
> > +- clock-names : Includes the following module clock source entries:
> > + "ftm0" (system clock),
> > + "ftm0_fix_sel" (fixed frequency clock),
> > + "ftm0_ext_sel" (external clock)
> > +- clocks : Must contain a clock specifier for each entry in clock-names.
> > +- fsl,pwm-counter-clk: The FTM PWM counter clock source, should be one of the
> > + entries in clock-names.
> > +- pinctrl-names: must contain a "default" entry.
> > +- pinctrl-NNN: One property must exist for each entry in pinctrl-names.
> > + See ../pinctrl/pinctrl-bindings.txt for details of the property values.
>
> Looks okay to me.
For consistency, shouldn't it also have:
"See ../clock/clock-bindings.txt for details of the property values"
where appropriate like is done under the pwm/pinctrl uses?
IMHO, referencing parent bindings all of the time should be a documented
best practice / requirement.
-Matt
> > +
> > +
> > +Example:
> > +
> > +pwm0: pwm at 40038000 {
> > + compatible = "fsl,vf610-ftm-pwm";
> > + reg = <0x40038000 0x1000>;
> > + #pwm-cells = <3>;
> > + clock-names = "ftm0", "ftm0_fix_sel", "ftm0_ext_sel";
> > + clocks = <&clks VF610_CLK_FTM0>,
> > + <&clks VF610_CLK_FTM0_FIX_SEL>,
> > + <&clks VF610_CLK_FTM0_EXT_SEL>;
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pinctrl_pwm0_1>;
> > + fsl,pwm-counter-clk = "ftm0_ext_sel";
> > +};
> > --
> > 1.8.0
> >
> >
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2013-10-26 13:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 6:13 [PATCHv5 0/4] Add Freescale FTM PWM driver Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` [PATCHv5 1/4] pwm: Add Freescale FTM PWM driver support Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` [PATCHv5 2/4] ARM: dts: Add Freescale FTM PWM node for VF610 Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` [PATCHv5 3/4] ARM: dts: Enables FTM PWM device for Vybrid VF610 TOWER board Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` [PATCHv5 4/4] Documentation: Add device tree bindings for Freescale FTM PWM Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-09-30 6:13 ` Xiubo Li
2013-10-08 13:56 ` Thierry Reding
2013-10-08 13:56 ` Thierry Reding
2013-10-22 2:33 ` Xiubo Li-B47053
2013-10-22 2:33 ` Xiubo Li-B47053
2013-10-25 20:12 ` Grant Likely
2013-10-25 20:12 ` Grant Likely
2013-10-26 13:02 ` Matt Porter [this message]
2013-10-26 13:02 ` Matt Porter
2013-10-27 13:50 ` Grant Likely
2013-10-27 13:50 ` Grant Likely
2013-09-30 8:20 ` [PATCHv5 0/4] Add Freescale FTM PWM driver Sascha Hauer
2013-09-30 8:20 ` Sascha Hauer
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=20131026130225.GJ29341@beef \
--to=matt.porter@linaro.org \
--cc=Li.Xiubo@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=r65073@freescale.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=s.hauer@pengutronix.de \
--cc=swarren@wwwdotorg.org \
--cc=t.figa@samsung.com \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.