[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160509200148.GA19811@rob-hp-laptop>
Date: Mon, 9 May 2016 15:01:48 -0500
From: Rob Herring <robh@...nel.org>
To: Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>
Cc: pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
thierry.reding@...il.com, bcousson@...libre.com, tony@...mide.com,
linux@....linux.org.uk, mchehab@....samsung.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pwm@...r.kernel.org, linux-omap@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-media@...r.kernel.org,
sre@...nel.org, pali.rohar@...il.com
Subject: Re: [PATCH 2/7] pwm: omap-dmtimer: Allow for setting dmtimer clock
source
On Sat, May 07, 2016 at 06:21:43PM +0300, Ivaylo Dimitrov wrote:
> OMAP GP timers can have different input clocks that allow different PWM
> frequencies. However, there is no other way of setting the clock source but
> through clocks or clock-names properties of the timer itself. This limits
> PWM functionality to only the frequencies allowed by the particular clock
> source. Allowing setting the clock source by PWM rather than by timer
> allows different PWMs to have different ranges by not hard-wiring the clock
> source to the timer.
>
> Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>
> ---
> Documentation/devicetree/bindings/pwm/pwm-omap-dmtimer.txt | 4 ++++
> drivers/pwm/pwm-omap-dmtimer.c | 12 +++++++-----
> 2 files changed, 11 insertions(+), 5 deletions(-)
Acked-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists