From: Thierry Reding <thierry.reding@gmail.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: jonathanh@nvidia.com, linux-pwm@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] pwm: tegra: Read PWM clock source rate in driver init
Date: Thu, 13 Apr 2017 17:36:32 +0200 [thread overview]
Message-ID: <20170413153632.GE27388@ulmo.ba.sec> (raw)
In-Reply-To: <1492092628-843-1-git-send-email-ldewangan@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
On Thu, Apr 13, 2017 at 07:40:27PM +0530, Laxman Dewangan wrote:
> It is required to know the PWM clock source frequency to
> calculate the PWM period.
>
> In driver, the clock source frequency of the PWM does not
> get change and, hence, get the clock source frequency in
> driver initi. Get this values later for period calculation
> from pwm_config().
>
> This will help in avoiding the clock call for getting clock rate
> in the pwm_config() each time.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> drivers/pwm/pwm-tegra.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-04-13 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 14:10 [PATCH 1/2] pwm: tegra: Read PWM clock source rate in driver init Laxman Dewangan
2017-04-13 14:10 ` Laxman Dewangan
2017-04-13 14:10 ` [PATCH 2/2] pwm: tegra: Set maximum pwm clock source per SoC tapeout Laxman Dewangan
2017-04-13 14:10 ` Laxman Dewangan
2017-04-13 15:27 ` Thierry Reding
[not found] ` <20170413152738.GB27388-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>
2017-04-13 17:17 ` Laxman Dewangan
2017-04-13 17:17 ` Laxman Dewangan
2017-04-13 15:36 ` 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=20170413153632.GE27388@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-tegra@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.