From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC] clk: rockchip: Fix CPLL setup issue
Date: Mon, 29 Sep 2025 10:44:27 +0200 [thread overview]
Message-ID: <aNpG60G_MbXKdprD@pengutronix.de> (raw)
In-Reply-To: <CAP1tNvRnHbCoi=29u_6WbXbD_CZ1kc01deppba4WuWW5mrcMXg@mail.gmail.com>
On Mon, Sep 29, 2025 at 11:29:04AM +0300, Alexander Shiyan wrote:
> Hello.
>
> > On Fri, Sep 26, 2025 at 04:15:14PM +0300, Alexander Shiyan wrote:
> > > This is a dirty patch to solve the RK3588 CPLL clock setup issue.
> > > It's taken from the Rockchip U-Boot repository [1].
> > > Any ideas on how to improve it?
> > >
> > > [1] https://github.com/rockchip-linux/u-boot/commit/bd11beba4f997b62809d24eba30a8713c8bbeb81
> ...
> > > + /* Barebox addition */
> > > + if (pll->reg_base - pll->ctx->reg_base == 0x1a0) {
> > > + /* Determine CPLL clock and patch clk_bisrintf_pllsrc_en back */
> > > + writel(HIWORD_UPDATE(0, BIT(1), 0),
> > > + pll->ctx->reg_base + 0x84c);
> > > + }
> >
> > Resetting this bit is not in the U-Boot patch you reference. Do we need
> > this?
>
> Yes.
> https://github.com/rockchip-linux/u-boot/commit/7560cacdd3a68bb475f23b4249a98025c89064d4
Ah, alright, they fixed it in a later commit. I only looked at the
commit you referenced. So please reference both in the commit message.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2025-09-29 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 13:15 Alexander Shiyan
2025-09-29 8:12 ` Sascha Hauer
2025-09-29 8:29 ` Alexander Shiyan
2025-09-29 8:44 ` Sascha Hauer [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=aNpG60G_MbXKdprD@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@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