From: Stephen Boyd <sboyd@kernel.org>
To: Andre Przywara <andre.przywara@arm.com>,
Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Samuel Holland <samuel@sholland.org>
Cc: linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev,
Philippe Simons <simons.philippe@gmail.com>
Subject: Re: [RFC PATCH] clk: sunxi-ng: h616: Reparent CPU clock during frequency changes
Date: Mon, 13 Jan 2025 10:59:58 -0800 [thread overview]
Message-ID: <ff960baf02e6aa6fb93fe9a4584689ad.sboyd@kernel.org> (raw)
In-Reply-To: <20241025105620.1891596-1-andre.przywara@arm.com>
Quoting Andre Przywara (2024-10-25 03:56:20)
> The H616 user manual recommends to re-parent the CPU clock during
> frequency changes of the PLL, and recommends PLL_PERI0(1X), which runs
> at 600 MHz. Also it asks to disable and then re-enable the PLL lock bit,
> after the factor changes have been applied.
>
> Add clock notifiers for the PLL and the CPU mux clock, using the existing
> notifier callbacks, and tell them to use mux 4 (the PLL_PERI0(1X) source),
> and bit 29 (the LOCK_ENABLE) bit. The existing code already follows the
> correct algorithms.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2025-01-13 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 10:56 [RFC PATCH] clk: sunxi-ng: h616: Reparent CPU clock during frequency changes Andre Przywara
2024-10-25 14:49 ` Chen-Yu Tsai
2024-10-25 15:05 ` Andre Przywara
2024-10-28 20:10 ` Philippe Simons
2024-11-08 20:14 ` Evgeny Boger
2024-11-08 22:34 ` Andre Przywara
2024-11-08 23:14 ` Evgeny Boger
2024-11-10 12:33 ` Chen-Yu Tsai
2025-01-13 14:44 ` Andre Przywara
2025-01-13 15:33 ` Chen-Yu Tsai
2025-01-13 18:59 ` 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=ff960baf02e6aa6fb93fe9a4584689ad.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=andre.przywara@arm.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mturquette@baylibre.com \
--cc=samuel@sholland.org \
--cc=simons.philippe@gmail.com \
--cc=wens@csie.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 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.