From: Chen-Yu Tsai <wens@kernel.org>
To: Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Arun Iyengar <aiyengar1990@gmail.com>
Cc: Andre Przywara <andre.przywara@arm.com>,
Maxime Ripard <mripard@kernel.org>,
Philippe Simons <simons.philippe@gmail.com>,
Ilya Titov <ilya.titov@wirenboard.com>,
linux-clk@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] clk: sunxi-ng: h616: PLL output gate and GPU notifier order
Date: Tue, 17 Nov 2026 00:59:08 +0800 [thread overview]
Message-ID: <179484834812.3674093.743014872311780954.b4-ty@kernel.org> (raw)
In-Reply-To: <20261116-h616-pll-output-gate-v2-0-a418026ffae6@gmail.com>
On Mon, 16 Nov 2026 08:45:06 +0000, Arun Iyengar wrote:
> Patch 1 gates the H616 PLLs with their output enable bit instead of
> powering them down. Patch 2 registers the GPU PLL notifier before the
> mux notifier, as Ilya Titov's 0ec5e7572ddc did for the CPU.
>
> No Cc: stable: the patch 1 crash needs out-of-tree H616 HDMI, and the
> old GPU notifier order never failed here.
>
> [...]
Applied to sunxi/clk-for-7.5 in sunxi, thanks!
[1/2] clk: sunxi-ng: h616: Gate the PLLs with their output enable bit
https://git.kernel.org/sunxi/linux/c/5aae0639bcc6
[2/2] clk: sunxi-ng: h616: Register GPU PLL notifier before mux notifier
https://git.kernel.org/sunxi/linux/c/3f8438336a3b
Best regards,
--
Chen-Yu Tsai <wens@kernel.org>
prev parent reply other threads:[~2026-11-16 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 8:45 Arun Iyengar via B4 Relay
2026-11-16 8:45 ` [PATCH v2 1/2] clk: sunxi-ng: h616: Gate the PLLs with their output enable bit Arun Iyengar via B4 Relay
2026-11-16 8:45 ` [PATCH v2 2/2] clk: sunxi-ng: h616: Register GPU PLL notifier before mux notifier Arun Iyengar via B4 Relay
2026-11-16 16:59 ` Chen-Yu Tsai [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=179484834812.3674093.743014872311780954.b4-ty@kernel.org \
--to=wens@kernel.org \
--cc=aiyengar1990@gmail.com \
--cc=andre.przywara@arm.com \
--cc=bmasney+clk@redhat.com \
--cc=ilya.titov@wirenboard.com \
--cc=jbrunet+clk@baylibre.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=samuel@sholland.org \
--cc=sboyd@kernel.org \
--cc=simons.philippe@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
all inboxes | Powered by JetHome®