From: Stephen Warren <swarren@wwwdotorg.org>
To: Xiubo Li <Li.Xiubo@freescale.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: r65073@freescale.com, thierry.reding@gmail.com,
s.hauer@pengutronix.de, t.figa@samsung.com,
grant.likely@linaro.org, linux@arm.linux.org.uk, rob@landley.net,
ian.campbell@citrix.com, mark.rutland@arm.com,
pawel.moll@arm.com, rob.herring@calxeda.com,
linux-arm-kernel@lists.infradead.org, linux-pwm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCHv4 4/4] Documentation: Add device tree bindings for Freescale FTM PWM.
Date: Fri, 13 Sep 2013 16:34:18 -0600 [thread overview]
Message-ID: <523392EA.6050909@wwwdotorg.org> (raw)
In-Reply-To: <1379051922-4930-5-git-send-email-Li.Xiubo@freescale.com>
On 09/12/2013 11:58 PM, Xiubo Li wrote:
> This adds the Document for Freescale FTM PWM driver under
> Documentation/devicetree/bindings/pwm/.
> diff --git a/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt b/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt
> +Required properties:
> +- 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 an entry list for entries in clock-names.
s/an entry list/a clock specifier/
s/for entries/for each entry/
> +- fsl,pwm-counter-clk: The FTM PWM counter clock source, should be one of the
> + entries in clock-names.
So the IP block has 3 input clocks, and also a mux to select which one
to use? That sounds slightly unusual, but possible.
If there is really only 1 clock input to the IP block, and the mux is
part of some other module, then this binding should have only 1 entry in
clocks.
> +- For each channel's pinctrl, the "chN-active" and "chN-idle" states should be
> + implemented at the same time.
I still don't believe that multiple pinctrl states active at once is
something that the pinctrl bindings conceptually support. CC+=LinusW, do
we want to allow this?
Assuming this is allowed, you'd want to write something more like the
following:
pinctrl-names: Must include "chN-active" and "chN-idle" for each channel
ID N in range 0..7.
pinctrl-NNN: One property must exist for each entry in pinctrl-names.
See ../pinctrl/pinctrl-bindings.txt for details of the property values.
> +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 = "ch0-active", "ch0-idle", "ch1-active", "ch1-idle",
> + ....;
> + pinctrl-0 = <&pinctrl_pwm0_ch0_active>;
> + pinctrl-1 = <&pinctrl_pwm0_ch0_idle>;
> + pinctrl-2 = <&pinctrl_pwm0_ch1_active>;
> + pinctrl-3 = <&pinctrl_pwm0_ch1_idle>;
> + ...
> + fsl,pwm-counter-clk = "ftm0_ext_sel";
> +};
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv4 4/4] Documentation: Add device tree bindings for Freescale FTM PWM.
Date: Fri, 13 Sep 2013 16:34:18 -0600 [thread overview]
Message-ID: <523392EA.6050909@wwwdotorg.org> (raw)
In-Reply-To: <1379051922-4930-5-git-send-email-Li.Xiubo@freescale.com>
On 09/12/2013 11:58 PM, Xiubo Li wrote:
> This adds the Document for Freescale FTM PWM driver under
> Documentation/devicetree/bindings/pwm/.
> diff --git a/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt b/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt
> +Required properties:
> +- 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 an entry list for entries in clock-names.
s/an entry list/a clock specifier/
s/for entries/for each entry/
> +- fsl,pwm-counter-clk: The FTM PWM counter clock source, should be one of the
> + entries in clock-names.
So the IP block has 3 input clocks, and also a mux to select which one
to use? That sounds slightly unusual, but possible.
If there is really only 1 clock input to the IP block, and the mux is
part of some other module, then this binding should have only 1 entry in
clocks.
> +- For each channel's pinctrl, the "chN-active" and "chN-idle" states should be
> + implemented at the same time.
I still don't believe that multiple pinctrl states active at once is
something that the pinctrl bindings conceptually support. CC+=LinusW, do
we want to allow this?
Assuming this is allowed, you'd want to write something more like the
following:
pinctrl-names: Must include "chN-active" and "chN-idle" for each channel
ID N in range 0..7.
pinctrl-NNN: One property must exist for each entry in pinctrl-names.
See ../pinctrl/pinctrl-bindings.txt for details of the property values.
> +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 = "ch0-active", "ch0-idle", "ch1-active", "ch1-idle",
> + ....;
> + pinctrl-0 = <&pinctrl_pwm0_ch0_active>;
> + pinctrl-1 = <&pinctrl_pwm0_ch0_idle>;
> + pinctrl-2 = <&pinctrl_pwm0_ch1_active>;
> + pinctrl-3 = <&pinctrl_pwm0_ch1_idle>;
> + ...
> + fsl,pwm-counter-clk = "ftm0_ext_sel";
> +};
next prev parent reply other threads:[~2013-09-13 22:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 5:58 [PATCHv4 0/4] Add Freescale FTM PWM driver Xiubo Li
2013-09-13 5:58 ` Xiubo Li
2013-09-13 5:58 ` Xiubo Li
2013-09-13 5:58 ` Xiubo Li
2013-09-13 5:58 ` [PATCHv4 1/4] pwm: Add Freescale FTM PWM driver support Xiubo Li
2013-09-13 5:58 ` Xiubo Li
2013-09-13 5:58 ` Xiubo Li
2013-09-13 5:58 ` [PATCHv4 2/4] ARM: dts: Add Freescale FTM PWM node for VF610 Xiubo Li
2013-09-13 5:58 ` Xiubo Li
2013-09-13 5:58 ` Xiubo Li
2013-09-13 5:58 ` [PATCHv4 3/4] ARM: dts: Enables FTM PWM device for Vybrid VF610 TOWER board Xiubo Li
2013-09-13 5:58 ` Xiubo Li
2013-09-13 5:58 ` Xiubo Li
2013-09-13 5:58 ` [PATCHv4 4/4] Documentation: Add device tree bindings for Freescale FTM PWM Xiubo Li
2013-09-13 5:58 ` Xiubo Li
2013-09-13 5:58 ` Xiubo Li
2013-09-13 22:34 ` Stephen Warren [this message]
2013-09-13 22:34 ` Stephen Warren
2013-09-16 2:49 ` Xiubo Li-B47053
2013-09-16 2:49 ` Xiubo Li-B47053
2013-09-16 2:49 ` Xiubo Li-B47053
2013-09-17 10:33 ` Sascha Hauer
2013-09-17 10:33 ` 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=523392EA.6050909@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Li.Xiubo@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=linus.walleij@linaro.org \
--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=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.