public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@nabladev.com>
To: nobuhiro.iwamatsu.x90@mail.toshiba
Cc: claudiu.beznea@tuxon.dev, pavel@nabladev.com,
	cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] [PATCH 6.1.y-cip 1/1] arm64: dts: renesas: rzg3s-smarc-som: Set bypass for Versa3 PLL2
Date: Tue, 7 Apr 2026 13:36:13 +0200	[thread overview]
Message-ID: <adTsLWXKfaKFJV8l@duo.ucw.cz> (raw)
In-Reply-To: <TY7PR01MB14818351766CF1AF2A8D2C3BECD5AA@TY7PR01MB14818.jpnprd01.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 3009 bytes --]

Hi!

> > commit 6dcbb6f070cccabc6a13d640a5a84de581fdd761 upstream.
> > 
> > The default settings for the Versa3 device on the Renesas RZ/G3S SMARC SoM board have PLL2 disabled. PLL2 was later
> > enabled together with audio support, as it is required to support both 44.1 kHz and 48 kHz audio.
> > 
> > With PLL2 enabled, it was observed that Linux occasionally either hangs during boot (the last log message being related
> > to the I2C probe) or randomly crashes. This was mainly reproducible on cold boots. During debugging, it was also noticed
> > that the Unicode replacement character ( ) sometimes appears on the serial console. Further investigation traced this to
> > the configuration applied through the Versa3 register at offset 0x1c, which controls PLL enablement.
> > 
> > The appearance of the Unicode replacement character suggested an issue with the SoC reference clock. The RZ/G3S
> > reference clock is provided by the Versa3 clock generator (REF output).
> > 
> > After checking with the Renesas Versa3 hardware team, it was found that this is related to the PLL2 lock bit being set
> > through the renesas,settings DT property.
> > 
> > The PLL lock bit must be set to avoid unstable clock output from the PLL.
> > However, due to the Versa3 hardware design, when a PLL lock bit is set, all outputs (including the REF clock) are
> > temporarily disabled until the configured PLLs become stable.
> > 
> > As an alternative, the bypass bit can be used. This does not interrupt the
> > PLL2 output or any other Versa3 outputs, but it may result in temporary instability on PLL2 output while the configuration
> > is applied. Since PLL2 feeds only the audio path and audio is not used during early boot, this is acceptable and does not
> > affect system boot.
> > 
> > Drop the PLL2 lock bit and set the bypass bit instead.
> > 
> > This has been tested with more than 1000 cold boots.
> > 
> > Fixes: a94253232b04 ("arm64: dts: renesas: rzg3s-smarc-som: Add versa3 clock generator node")
> > Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> > Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > Link: https://patch.msgid.link/20260302135703.162601-1-claudiu.beznea.uj@bp.renesas.com
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> 
> I reviewed each version, looks good to me.
> If tests are OK and there is no comment, I can apply.
>   https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2433101088
>   https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2433102394
>   https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2433103164
> 
> Reviewed-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.x90@mail.toshiba>

Looks good to me, 5.10, 6.1 and 6.12 versions:

Reviewed-by: Pavel Machek <pavel@nabladev.com>

Best regards,
                                                                Pavel

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2026-04-07 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02 16:09 [PATCH 6.1.y-cip 1/1] arm64: dts: renesas: rzg3s-smarc-som: Set bypass for Versa3 PLL2 Claudiu
2026-04-07  0:39 ` nobuhiro.iwamatsu.x90
2026-04-07 11:36   ` Pavel Machek [this message]
2026-04-08  0:54     ` [cip-dev] " nobuhiro.iwamatsu.x90

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=adTsLWXKfaKFJV8l@duo.ucw.cz \
    --to=pavel@nabladev.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    /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