From: Stephen Boyd <sboyd@kernel.org>
To: Dinh Nguyen <dinguyen@kernel.org>, linux-clk@vger.kernel.org
Cc: dinguyen@kernel.org, mturquette@baylibre.com,
linux-stable@vger.kernel.org
Subject: Re: [PATCH] clk: socfpga: stratix10: fix rate calculation for pll clocks
Date: Fri, 11 Jan 2019 15:41:08 -0800 [thread overview]
Message-ID: <154725006827.169631.11387684968829410246@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20181218000614.30520-1-dinguyen@kernel.org>
Quoting Dinh Nguyen (2018-12-17 16:06:14)
> The main PLL calculation has a mistake. We should be using the
> multiplying the VCO frequency, not the parent clock frequency.
>
> Fixes: 07afb8db7340 ("clk: socfpga: stratix10: add clock driver for
> Stratix10 platform")
> Cc: linux-stable@vger.kernel.org
> Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
> ---
Applied to clk-fixes
prev parent reply other threads:[~2019-01-11 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 0:06 [PATCH] clk: socfpga: stratix10: fix rate calculation for pll clocks Dinh Nguyen
2019-01-11 23:41 ` Stephen Boyd [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=154725006827.169631.11387684968829410246@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-stable@vger.kernel.org \
--cc=mturquette@baylibre.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).