From: Yao Zi <me@ziyao.cc>
To: Ulf Hansson <ulfh@kernel.org>, Heiko Stuebner <heiko@sntech.de>,
Shawn Lin <shawn.lin@rock-chips.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Yao Zi <me@ziyao.cc>, Sergey Shtylyov <s.shtylyov@auroraos.dev>,
Midgy BALON <midgy971@gmail.com>,
Finley Xiao <finley.xiao@rock-chips.com>,
Frank Zhang <rmxpzlb@gmail.com>,
Chris Morgan <macromorgan@hotmail.com>,
Kevin Hilman <khilman@linaro.org>,
Caesar Wang <wxt@rock-chips.com>,
Elaine Zhang <zhangqing@rock-chips.com>
Cc: linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Error and deferred probe fixes to Rockchip PM domain driver
Date: Thu, 5 Nov 2026 00:12:55 +0000 [thread overview]
Message-ID: <20261105001257.1368266-1-me@ziyao.cc> (raw)
These issues were found after I upgraded a RK3528 board to v7.3 kernel.
Here's a configuration that I used to reproduce both of these two
problems[1].
Thanks for your time and review.
[1]: https://gist.github.com/ziyao233/a5ee8862d1baf21ad756cf4e959e14c3
Yao Zi (2):
pmdomain: rockchip: Only put clocks that have been successfully
obtained
pmdomain: rockchip: Don't log when of_clk_get() fails with
-EPROBE_DEFER
drivers/pmdomain/rockchip/pm-domains.c | 24 ++++++++++++++----------
1 file changed, 14 insertions(+), 10 deletions(-)
--
2.56.0
next reply other threads:[~2026-11-05 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 0:12 Yao Zi [this message]
2026-11-05 0:12 ` [PATCH 1/2] pmdomain: rockchip: Only put clocks that have been successfully obtained Yao Zi
2026-11-05 0:12 ` [PATCH 2/2] pmdomain: rockchip: Don't log when of_clk_get() fails with -EPROBE_DEFER Yao Zi
2026-11-05 20:47 ` Sergey Shtylyov
2026-11-06 8:50 ` Yao Zi
2026-11-06 20:37 ` Sergey Shtylyov
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=20261105001257.1368266-1-me@ziyao.cc \
--to=me@ziyao.cc \
--cc=finley.xiao@rock-chips.com \
--cc=heiko@sntech.de \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macromorgan@hotmail.com \
--cc=midgy971@gmail.com \
--cc=rmxpzlb@gmail.com \
--cc=s.shtylyov@auroraos.dev \
--cc=sebastian.reichel@collabora.com \
--cc=shawn.lin@rock-chips.com \
--cc=ulfh@kernel.org \
--cc=wxt@rock-chips.com \
--cc=zhangqing@rock-chips.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®