From: Thierry Reding <thierry.reding@gmail.com>
To: Claudiu.Beznea@microchip.com
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
Ludovic.Desroches@microchip.com,
linux-arm-kernel@lists.infradead.org, linux-pwm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] add support for the new SAM9X60's PWM controller
Date: Mon, 4 Mar 2019 11:58:49 +0100 [thread overview]
Message-ID: <20190304105849.GA5121@ulmo> (raw)
In-Reply-To: <1551113039-937-1-git-send-email-claudiu.beznea@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
On Mon, Feb 25, 2019 at 04:44:30PM +0000, Claudiu.Beznea@microchip.com wrote:
> From: Claudiu Beznea <claudiu.beznea@microchip.com>
>
> This series adds support for PWM controller of the new SAM9X60. The difference
> b/w this one and the provious AT91SAM9X5 is the counter size (32 bits compared
> with 16 bits on the previous version) thus, allowing to generate signals with
> bigger periods and duty cycles. This series, modifies the driver to take into
> account per IP counter size by embedding this information into driver's data.
>
> Changes in v3:
> - collect Acked-by tags
> - introduced patch 3/5 which changes the name of objects of type
> atmel_pwm_data
> - changed a bit commit message for patches 1/5 and 2/5
> - use mchp_sam9x60_pwm_data instead of atmel_pwm_data_v3 for SAM9X60
> compatible data
>
> Changes in v2:
> - add reviewed-by tag to DT inding patch
> - move PWM_MAXV2_PRD from patch 2/4 in patch 3/4
> - change commit description for patch 3/4
>
> Claudiu Beznea (5):
> pwm: atmel: add struct atmel_pwm_data
> pwm: atmel: add support for controllers with 32 bit counters
> pwm: atmel: rename objects of type atmel_pwm_data
> pwm: atmel: add support for SAM9X60's PWM controller
> pwm: atmel: add PWM binding for SAM9X60
>
> .../devicetree/bindings/pwm/atmel-pwm.txt | 1 +
> drivers/pwm/pwm-atmel.c | 117 ++++++++++++++-------
> 2 files changed, 79 insertions(+), 39 deletions(-)
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-03-04 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 16:44 [PATCH v3 0/5] add support for the new SAM9X60's PWM controller Claudiu.Beznea
2019-02-25 16:44 ` [PATCH v3 1/5] pwm: atmel: add struct atmel_pwm_data Claudiu.Beznea
2019-02-25 16:44 ` [PATCH v3 2/5] pwm: atmel: add support for controllers with 32 bit counters Claudiu.Beznea
2019-02-25 16:44 ` [PATCH v3 3/5] pwm: atmel: rename objects of type atmel_pwm_data Claudiu.Beznea
2019-02-25 16:44 ` [PATCH v3 4/5] pwm: atmel: add support for SAM9X60's PWM controller Claudiu.Beznea
2019-02-25 16:44 ` [PATCH v3 5/5] pwm: atmel: add PWM binding for SAM9X60 Claudiu.Beznea
2019-03-04 10:58 ` 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=20190304105849.GA5121@ulmo \
--to=thierry.reding@gmail.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).