From: Stephen Warren <swarren@wwwdotorg.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: linux-arm-kernel@lists.infradead.org, mturquette@linaro.org,
Prashant Gaikwad <pgaikwad@nvidia.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: tegra: pllc and pllxc should use pdiv_map
Date: Wed, 05 Jun 2013 10:22:02 -0600 [thread overview]
Message-ID: <51AF65AA.2000702@wwwdotorg.org> (raw)
In-Reply-To: <1370437007-25596-1-git-send-email-pdeschrijver@nvidia.com>
On 06/05/2013 06:56 AM, Peter De Schrijver wrote:
> The pllc and pllxc code weren't always using the correct pdiv_map to
> map between the post divider value and the hw p field. This could result
> in illegal values being programmed in the hw.
Tested-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: tegra: pllc and pllxc should use pdiv_map
Date: Wed, 05 Jun 2013 10:22:02 -0600 [thread overview]
Message-ID: <51AF65AA.2000702@wwwdotorg.org> (raw)
In-Reply-To: <1370437007-25596-1-git-send-email-pdeschrijver@nvidia.com>
On 06/05/2013 06:56 AM, Peter De Schrijver wrote:
> The pllc and pllxc code weren't always using the correct pdiv_map to
> map between the post divider value and the hw p field. This could result
> in illegal values being programmed in the hw.
Tested-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2013-06-05 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 12:56 [PATCH] clk: tegra: pllc and pllxc should use pdiv_map Peter De Schrijver
2013-06-05 12:56 ` Peter De Schrijver
2013-06-05 12:56 ` Peter De Schrijver
2013-06-05 16:22 ` Stephen Warren [this message]
2013-06-05 16:22 ` Stephen Warren
[not found] ` <1370437007-25596-1-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-11 23:45 ` Mike Turquette
2013-06-11 23:45 ` Mike Turquette
2013-06-11 23:45 ` Mike Turquette
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=51AF65AA.2000702@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.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 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.