From: Sascha Hauer <s.hauer@pengutronix.de>
To: Xiubo Li-B47053 <B47053@freescale.com>
Cc: Guo Shawn-R65073 <r65073@freescale.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"rob@landley.net" <rob@landley.net>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCHv2 4/4] Documentation: Add device tree bindings for Freescale FTM PWM.
Date: Mon, 2 Sep 2013 10:52:38 +0200 [thread overview]
Message-ID: <20130902085238.GR30088@pengutronix.de> (raw)
In-Reply-To: <1DD289F6464F0949A2FCA5AA6DC23F827F7831@039-SN2MPN1-011.039d.mgd.msft.net>
On Mon, Sep 02, 2013 at 02:38:53AM +0000, Xiubo Li-B47053 wrote:
> > Subject: Re: [PATCHv2 4/4] Documentation: Add device tree bindings for
> > Freescale FTM PWM.
> >
> ...
> > > +
> > > +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";
> > > + fsl,pwm-avaliable-chs = <0 3 5 6>;
> >
> > I don't think this proerty is useful. Just enable all channels. I think
> > this was mentioned before.
> >
> Yes.
> Actully this property is located in board level dts file.
> I have added and requested all the channels in SoC level dtsi file,
> and in board level dts file to tell the customer the limitation, I
> think is much safter and better.
Why should this be in the board file? A pwm that is not available should
simply not be referenced and thus be unused. No need to explicitly
disable it.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2013-09-02 8:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 9:48 [PATCHv2 0/4] Add Freescale FTM PWM driver for Vybrid VF610 TOWER Xiubo Li
2013-08-30 9:48 ` [PATCHv2 1/4] pwm: Add Freescale FTM PWM driver support Xiubo Li
2013-08-30 17:49 ` Sascha Hauer
2013-09-02 3:33 ` Xiubo Li-B47053
2013-09-02 8:56 ` Sascha Hauer
2013-09-03 4:17 ` Xiubo Li-B47053
2013-09-03 6:58 ` Sascha Hauer
2013-09-03 7:40 ` Xiubo Li-B47053
2013-08-30 9:48 ` [PATCHv2 2/4] ARM: dts: Add Freescale FTM PWM node for VF610 Xiubo Li
2013-08-30 9:48 ` [PATCHv2 3/4] ARM: dts: Enables FTM PWM device for Vybrid VF610 TOWER board Xiubo Li
2013-08-30 9:48 ` [PATCHv2 4/4] Documentation: Add device tree bindings for Freescale FTM PWM Xiubo Li
2013-08-30 17:30 ` Sascha Hauer
2013-09-02 2:38 ` Xiubo Li-B47053
2013-09-02 8:52 ` Sascha Hauer [this message]
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=20130902085238.GR30088@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=B47053@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=swarren@wwwdotorg.org \
--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 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).