From: Thierry Reding <thierry.reding@avionic-design.de>
To: Shiraz Hashim <shiraz.hashim@st.com>
Cc: linux-kernel@vger.kernel.org, spear-devel@list.st.com,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH V5] PWM: Add SPEAr PWM chip driver support
Date: Mon, 5 Nov 2012 10:04:51 +0100 [thread overview]
Message-ID: <20121105090451.GA5847@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <1351138153-584-1-git-send-email-shiraz.hashim@st.com>
[-- Attachment #1: Type: text/plain, Size: 2779 bytes --]
On Thu, Oct 25, 2012 at 09:39:13AM +0530, Shiraz Hashim wrote:
> Add support for PWM chips present on SPEAr platforms. These PWM
> chips support 4 channel output with programmable duty cycle and
> frequency.
>
> More details on these PWM chips can be obtained from relevant
> chapter of reference manual, present at following[1] location.
>
> 1. http://www.st.com/internet/mcu/product/251211.jsp
>
> Cc: Thierry Reding <thierry.reding@avionic-design.de>
> Signed-off-by: Shiraz Hashim <shiraz.hashim@st.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> Reviewed-by: Vipin Kumar <vipin.kumar@st.com>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> Changes:-
> V4 --> V5:
> * replace tab by space in structure element declaration
> * restructure probe to register pwm_chip at end when clk is prepared, and
> all initializations done.
> * move clk_enable/disable in probe under if block which checks "1340"
> compatibility
> * Replace (ret < 0) if condition by (!ret) at places where ret should be 0
> on success
>
> V3 --> V4:
> * simplify remove
> * maintain alphabetical order in Makefile
> * donot check for device node in probe
> * move few assignment lines in probe
>
> V2 --> V3:
> * remove "disabled" line from pwm dt binding documentation
> * remove un-necessary check on pwm chip (for NULL) in remove.
>
> V1 --> V2:
> * make proper reference to pwm and pwm chip
> * take care to capitalize PWM at appropriate places
> * fix compatible string to the SoC where pwm chip was introduced
> * Rename the documentation file to the name of driver
> * Fix cosmetic changes like names, function name alignment, paragraph
> formating, comments placement and formating, etc.
> * Group and associate the bit field definitions to their registers
> * Fix kerneldoc for structure definition
> * Use chip to name pwm device and pwm for the channel instance
> * Remove init section qualifiers
> * Remove ifdefs around device tree from code and add dependency on CONFIG_OF
> * prepare/unprepare clock once in probe/remove and just enable/disable
> at rest of the places.
> * Use _relaxed for readl/writel.
> * Fix pwm disable part in remove
>
> .../devicetree/bindings/pwm/spear-pwm.txt | 18 ++
> drivers/pwm/Kconfig | 11 +
> drivers/pwm/Makefile | 1 +
> drivers/pwm/pwm-spear.c | 276 ++++++++++++++++++++
> 4 files changed, 306 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pwm/spear-pwm.txt
> create mode 100644 drivers/pwm/pwm-spear.c
Applied, thanks.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-11-05 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 4:09 Shiraz Hashim
2012-10-25 4:24 ` Viresh Kumar
2012-11-05 9:04 ` Thierry Reding [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=20121105090451.GA5847@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=linux-kernel@vger.kernel.org \
--cc=shiraz.hashim@st.com \
--cc=spear-devel@list.st.com \
--cc=viresh.kumar@linaro.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
Powered by JetHome