From: Stephen Boyd <sboyd@codeaurora.org>
To: Ray Jui <rjui@broadcom.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Simran Rai <ssimran@broadcom.com>
Subject: Re: [PATCH] clk: iproc: Fix PLL output frequency calculation
Date: Mon, 19 Oct 2015 15:16:05 -0700 [thread overview]
Message-ID: <56256BA5.3090705@codeaurora.org> (raw)
In-Reply-To: <562566C1.8080409@broadcom.com>
On 10/19/2015 02:55 PM, Ray Jui wrote:
>
>
> On 15-10-19 02:49 PM, Stephen Boyd wrote:
>> On 10/16, Ray Jui wrote:
>>> From: Simran Rai <ssimran@broadcom.com>
>>>
>>> This patch affects the clocks that use fractional ndivider in their
>>> PLL output frequency calculation. Instead of 2^20 divide factor, the
>>> clock's ndiv integer shift was used. Fixed the bug by replacing ndiv
>>> integer shift with 2^20 factor.
>>>
>>> Signed-off-by: Simran Rai <ssimran@broadcom.com>
>>> Signed-off-by: Ray Jui <rjui@broadcom.com>
>>> Reviewed-by: Scott Branden <sbranden@broadcom.com>
>>> ---
>>
>> Did you want any Fixes: tag so this goes back to stable?
>>
>
> Yes, we want this fix to go back to the stable kernel.
>
> I will re-submit the patch with the Fixes: tag and at the same time cc
> stable@vger.kernel.org .
Please just tell me the commit that this fixes, I can add the tag and
apply to the right tree then.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-10-19 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 22:44 [PATCH] Fix iProc PLL output clock frequency calculation Ray Jui
2015-10-16 22:44 ` [PATCH] clk: iproc: Fix PLL output " Ray Jui
2015-10-19 21:49 ` Stephen Boyd
2015-10-19 21:55 ` Ray Jui
2015-10-19 22:16 ` Stephen Boyd [this message]
2015-10-21 9:46 ` Michael 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=56256BA5.3090705@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rjui@broadcom.com \
--cc=ssimran@broadcom.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;
as well as URLs for NNTP newsgroup(s).