From: m18063 <Claudiu.Beznea@microchip.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: <thierry.reding@gmail.com>, <robh+dt@kernel.org>,
<pawel.moll@arm.com>, <mark.rutland@arm.com>,
<ijc+devicetree@hellion.org.uk>, <galak@codeaurora.org>,
<boris.brezillon@free-electrons.com>, <linux-pwm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] drivers: pwm: pwm-atmel: add support to allow run time changing of pwm parameters
Date: Thu, 23 Feb 2017 17:22:36 +0200 [thread overview]
Message-ID: <8123991c-5e3c-ad5c-bbf3-bcd7ee2a5e5e@microchip.com> (raw)
In-Reply-To: <20170223103239.tv6nodddlar5l5fl@piout.net>
On 23.02.2017 12:32, Alexandre Belloni wrote:
> On 23/02/2017 at 12:25:58 +0200, m18063 wrote:
>>> It is probably worth switching to atomic PWM instead of changing this
>>> function. This would simplify the whole driver.
>> I was thinking to switch to atomic PWM in a future patch.
> Then why wait ?
>
>
I wanted to do it in progressively:
- enable the support for SAMA5d2
- make it work based on what is currently implemented
- add atomic PWM support.
Anyway, please ignore this patch. I will do it in atomic
PWM way.
Thank you,
Claudiu
prev parent reply other threads:[~2017-02-23 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 8:38 [PATCH 0/2] drivers: pwm: add pwm support for sama5d2 Claudiu Beznea
2017-02-23 8:38 ` [PATCH 1/2] drivers: pwm: pwm-atmel: add support for pwm on sama5d2 Claudiu Beznea
2017-02-23 9:16 ` Alexandre Belloni
2017-02-27 15:23 ` m18063
2017-02-23 8:38 ` [PATCH 2/2] drivers: pwm: pwm-atmel: add support to allow run time changing of pwm parameters Claudiu Beznea
2017-02-23 9:21 ` Alexandre Belloni
2017-02-23 10:25 ` m18063
2017-02-23 10:32 ` Boris Brezillon
2017-02-23 10:32 ` Alexandre Belloni
2017-02-23 15:22 ` m18063 [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=8123991c-5e3c-ad5c-bbf3-bcd7ee2a5e5e@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--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=pawel.moll@arm.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®