From: Chanwoo Choi <cw00.choi@samsung.com>
To: Andrzej Hajda <a.hajda@samsung.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: "Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Tomasz Figa" <tomasz.figa@gmail.com>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Kukjin Kim" <kgene@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"moderated list:SAMSUNG SOC CLOCK DRIVERS"
<linux-samsung-soc@vger.kernel.org>,
"open list:COMMON CLK FRAMEWORK" <linux-clk@vger.kernel.org>,
"Chanwoo Choi (gmail)" <cwchoi00@gmail.com>,
"\"최찬우 (samsung.com)\"" <chanwoo@kernel.org>,
최찬우 <cw00.choi@samsung.com>
Subject: Re: [PATCH 4/7] clk: samsung: exynos5433: fix PLL rates
Date: Wed, 14 Feb 2018 14:45:43 +0900 [thread overview]
Message-ID: <5A83CD07.3060008@samsung.com> (raw)
In-Reply-To: <20180213134032.30235-5-a.hajda@samsung.com>
Hi Sylwester and Andrzej,
Exynos5433 TRM shows different PLL frequency from the calculated value. Actually, I'm not sure which value is the correct value between TRM's value and real calculated value.
If we only consider the equation, I agree that we have to replace them with real calculated value with equation. But, TRM shows the diagram of clock domain which contains the multiple IPs. And each diagram specifies the required source clock rate of each child IP. Maybe, this source clock rate might be calculated from the PLL rate provided by TRM. (even if it's different from real calculated value).
Although the real rate is a little bit incorrect, we might better to keep PLL rate provided by TRM in order to get the required source clock of child IPs as the TRM. If we modify the PLL rate provided by TRM, the source clock rate of child IP might be different from TRM.
Basically, I have no objection of this patch. Just I think that need to check it.
Regards,
Chanwoo Choi
On 2018년 02월 13일 22:40, Andrzej Hajda wrote:
> Declared rates did not match rates generated by PLL.
> As a result driver behaved inconsitently.
>
> Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
> ---
> drivers/clk/samsung/clk-exynos5433.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/clk/samsung/clk-exynos5433.c b/drivers/clk/samsung/clk-exynos5433.c
> index db270908037a..335bebfa21c0 100644
> --- a/drivers/clk/samsung/clk-exynos5433.c
> +++ b/drivers/clk/samsung/clk-exynos5433.c
> @@ -729,7 +729,7 @@ static const struct samsung_pll_rate_table exynos5433_pll_rates[] __initconst =
> PLL_35XX_RATE(800000000U, 400, 6, 1),
> PLL_35XX_RATE(733000000U, 733, 12, 1),
> PLL_35XX_RATE(700000000U, 175, 3, 1),
> - PLL_35XX_RATE(667000000U, 222, 4, 1),
> + PLL_35XX_RATE(666000000U, 222, 4, 1),
> PLL_35XX_RATE(633000000U, 211, 4, 1),
> PLL_35XX_RATE(600000000U, 500, 5, 2),
> PLL_35XX_RATE(552000000U, 460, 5, 2),
> @@ -757,12 +757,12 @@ static const struct samsung_pll_rate_table exynos5433_pll_rates[] __initconst =
> /* AUD_PLL */
> static const struct samsung_pll_rate_table exynos5433_aud_pll_rates[] __initconst = {
> PLL_36XX_RATE(400000000U, 200, 3, 2, 0),
> - PLL_36XX_RATE(393216000U, 197, 3, 2, -25690),
> + PLL_36XX_RATE(393216003U, 197, 3, 2, -25690),
> PLL_36XX_RATE(384000000U, 128, 2, 2, 0),
> - PLL_36XX_RATE(368640000U, 246, 4, 2, -15729),
> - PLL_36XX_RATE(361507200U, 181, 3, 2, -16148),
> - PLL_36XX_RATE(338688000U, 113, 2, 2, -6816),
> - PLL_36XX_RATE(294912000U, 98, 1, 3, 19923),
> + PLL_36XX_RATE(368639991U, 246, 4, 2, -15729),
> + PLL_36XX_RATE(361507202U, 181, 3, 2, -16148),
> + PLL_36XX_RATE(338687988U, 113, 2, 2, -6816),
> + PLL_36XX_RATE(294912002U, 98, 1, 3, 19923),
> PLL_36XX_RATE(288000000U, 96, 1, 3, 0),
> PLL_36XX_RATE(252000000U, 84, 1, 3, 0),
> { /* sentinel */ }
>
next prev parent reply other threads:[~2018-02-14 5:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180213134056eucas1p270dae5e31eeb96f5c317fe512d761ddd@eucas1p2.samsung.com>
2018-02-13 13:40 ` [PATCH 0/7] clk: samsung: fix PLL rates Andrzej Hajda
2018-02-13 13:40 ` [PATCH 1/7] clk: samsung: exynos3250: " Andrzej Hajda
2018-02-13 14:41 ` Krzysztof Kozlowski
2018-02-16 10:00 ` Sylwester Nawrocki
2018-02-16 10:06 ` Krzysztof Kozlowski
2018-02-14 5:03 ` Chanwoo Choi
2018-02-16 11:58 ` Sylwester Nawrocki
2018-02-16 12:03 ` Sylwester Nawrocki
2018-02-13 13:40 ` [PATCH 2/7] clk: samsung: exynos5250: " Andrzej Hajda
2018-02-14 5:07 ` Chanwoo Choi
2018-02-13 13:40 ` [PATCH 3/7] clk: samsung: exynos5260: " Andrzej Hajda
2018-02-13 13:40 ` [PATCH 4/7] clk: samsung: exynos5433: " Andrzej Hajda
2018-02-14 5:45 ` Chanwoo Choi [this message]
2018-02-14 8:36 ` Andrzej Hajda
2018-02-15 14:23 ` Sylwester Nawrocki
2018-02-13 13:40 ` [PATCH 5/7] clk: samsung: exynos7: " Andrzej Hajda
2018-02-13 13:40 ` [PATCH 6/7] clk: samsung: s3c2410: " Andrzej Hajda
2018-02-13 13:40 ` [PATCH 7/7] clk: samsung: add compile time PLL rate validators Andrzej Hajda
2018-02-13 14:25 ` Krzysztof Kozlowski
2018-02-14 7:53 ` [PATCH v2 " Andrzej Hajda
2018-02-15 7:55 ` [PATCH 0/7] clk: samsung: fix PLL rates Tomasz Figa
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=5A83CD07.3060008@samsung.com \
--to=cw00.choi@samsung.com \
--cc=a.hajda@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=chanwoo@kernel.org \
--cc=cwchoi00@gmail.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mturquette@baylibre.com \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=tomasz.figa@gmail.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