From: Xiubo Li <Li.Xiubo@freescale.com>
To: r65073@freescale.com, thierry.reding@gmail.com
Cc: 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,
grant.likely@linaro.org, t.figa@samsung.com,
linux-arm-kernel@lists.infradead.org
Subject: [RFCv2][PATCHv5 0/4] Add Freescale FTM PWM driver.
Date: Wed, 30 Oct 2013 14:23:20 +0800 [thread overview]
Message-ID: <1383114204-17264-1-git-send-email-Li.Xiubo@freescale.com> (raw)
Hello,
This patch series is the Freescale FTM PWM implementation. And there are 8 channels most supported by the FTM PWM. This implementation is only compatible with device tree definition.
This patch series is based on linux-next and has been tested on Vybrid VF610 Tower board using device tree.
Changes in RFCv2 of PATVHv5:
- Remove "fsl,pwm-counter-clk"(all the four patches are modified).
Changes in v5:
- Remove active/idle pinctrl stuff.
Changes in v4:
- Check for the result and return an error for devm_kzalloc().
- Move pinmux setting from the SoC file to the board specific file.
- Revise the written mistake of 'ret |= FTMSC_CLKEXT;' --> 'reg |= FTMSC_CLKEXT;'.
Changes in v3:
- Remove "availabe" field.
- Remove "fsl,pwm-avaliable-chs" property.
- ...
Changes in v2:
- Remove PWM CPWM/EPWM feature and sysfs.
- Remove some redundant code.
- Revise some code for more readable.
- Remove "fsl,pwm-clk-ps", "fsl,pwm-number", "fsl,pwm-channels",etc.
- Add "fsl,pwm-avaliable-chs", "fsl,pwm-counter-clk", etc.
- Support 8 channels default in dtsi file.
- Add counter clock source selection.
- Rename some function name, macro name, etc.
- Use PWM's and OF's existing function interfaces.
- Split clk_unprepare_enable to clk_unprepare and clk_enable,etc.
- ...
Added in v1:
- Add Freescale FTM PWM driver support.
- Add Freescale FTM PWM node for VF610.
- Enable Enables FTM PWM device for Vybrid VF610 TOWER.
- Add device tree bindings for Freescale.
next reply other threads:[~2013-10-30 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 6:23 Xiubo Li [this message]
2013-10-30 6:23 ` [RFCv2][PATCHv5 1/4] pwm: Add Freescale FTM PWM driver support Xiubo Li
2013-10-30 6:23 ` [RFCv2][PATCHv5 2/4] ARM: dts: Add Freescale FTM PWM node for VF610 Xiubo Li
2013-10-30 6:23 ` [RFCv2][PATCHv5 3/4] ARM: dts: Enables FTM PWM device for Vybrid VF610 TOWER board Xiubo Li
2013-10-30 6:23 ` [RFCv2][PATCHv5 4/4] Documentation: Add device tree bindings for Freescale FTM PWM Xiubo Li
[not found] ` <1383114204-17264-5-git-send-email-Li.Xiubo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-10-30 14:16 ` Kumar Gala
2013-11-01 6:34 ` [RFCv2][PATCHv5 0/4] Add Freescale FTM PWM driver Li Xiubo
2013-11-07 7:00 ` Li Xiubo
2013-11-11 9:30 ` Thierry Reding
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=1383114204-17264-1-git-send-email-Li.Xiubo@freescale.com \
--to=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 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).