mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Chuan Liu <chuan.liu@amlogic.com>
Cc: linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] clk: meson: Fix an issue with inaccurate hifi_pll frequency
Date: Wed, 4 Sep 2024 15:31:29 +0800	[thread overview]
Message-ID: <15cd5d2a-61e3-40e1-a494-579b7e185dae@amlogic.com> (raw)
In-Reply-To: <20240904071817.489245-1-chuan.liu@amlogic.com>


Sorry, The email was sent by mistake, please ignore it.


On 2024/9/4 15:18, chuan.liu@amlogic.com wrote:
> From: Chuan Liu <chuan.liu@amlogic.com>
>
> Some PLLs with fractional multipliers have fractional denominators that
> are fixed to "100000" instead of the previous "(1 << pll->frac.width)".
>
> The hifi_pll for both C3 and S4 supports a fractional multiplier and has
> a fixed fractional denominator of "100000".
>
> Here are the results of the C3-based command tests (already defined
> CLOCK_ALLOW_WRITE_DEBUGFS):
> # echo 491520000 > /sys/kernel/debug/clk/hifi_pll/clk_rate
> # cat /sys/kernel/debug/clk/hifi_pll/clk_rate
> 491520000
> # echo 1 > /sys/kernel/debug/clk/hifi_pll/clk_prepare_enable
> # cat /sys/kernel/debug/meson-clk-msr/clks/hifi_pll_clk
> 491515625       +/-15625Hz
> # devmem 0xfe008100 32
> 0xD00304A3
> # devmem 0xfe008104 32
> 0x00014820
>
> Based on the register information read above, it can be obtained:
> m = 0xA3 = 0d163;
> n = 0x1 = 0d1
> frac = 0x14820 = 0d84000
> od = 0x3 = 0d3
>
> hifi_pll calculates the output frequency:
> calc_rate = xtal_rate / n * (m + (frac / frac_max)) >> od;
> calc_rate = 24000000 / 1 * (163 + (84000 / 100000)) >> 3;
> calc_rate = 491520000
>
> clk_rate, msr_rate, and calc_rate all match.
>
> The test and calculation results of S4 are consistent with those of C3,
> which will not be repeated here.
>
> To: Neil Armstrong <neil.armstrong@linaro.org>
> To: Jerome Brunet <jbrunet@baylibre.com>
> To: Michael Turquette <mturquette@baylibre.com>
> To: Stephen Boyd <sboyd@kernel.org>
> To: Kevin Hilman <khilman@baylibre.com>
> To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Cc:  <linux-amlogic@lists.infradead.org>
> Cc:  <linux-clk@vger.kernel.org>
> Cc:  <linux-arm-kernel@lists.infradead.org>
> Cc:  <linux-kernel@vger.kernel.org>
> Signed-off-by: Chuan Liu <chuan.liu@amlogic.com>
>
>
> --- b4-submit-tracking ---
> # This section is used internally by b4 prep for tracking purposes.
> {
>    "series": {
>      "revision": 1,
>      "change-id": "20240904-fix_clk-668f7a1a2b16",
>      "prefixes": []
>    }
> }

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2024-09-04  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04  7:18 chuan.liu
2024-09-04  7:31 ` Chuan Liu [this message]
2024-09-04  7:20 chuan.liu
2024-09-04  7:32 ` Chuan Liu

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=15cd5d2a-61e3-40e1-a494-579b7e185dae@amlogic.com \
    --to=chuan.liu@amlogic.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®