Linux clock framework development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Rudraksha Gupta" <guptarud@gmail.com>
Cc: linux-clk@vger.kernel.org, mfd@lists.linux.dev, lee@kernel.org,
	devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 2/2] clk: rk808: Select the clock function of CLK32KOUT2 on the RK818
Date: Tue, 25 Aug 2026 05:22:11 +0000	[thread overview]
Message-ID: <20260825052211.775701F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260824-ppp_connectivity-v2-2-a4b0e11cd62c@gmail.com>

> From: Martijn Braam <martijn@brixit.nl>
> 
> On the RK818 the CLK32KOUT2 pin is shared between the 32.768 kHz clock
> output and a recovery function, selected by bit 1 of RK808_CLK32OUT_REG.
> CLK32KOUT2_EN only takes effect on the clock function, so the output can
> be enabled and still be silent. The datasheet resets the register to
> zero, but that cannot be relied on: on the Pine64 PinePhone Pro it reads
> 0x03 once Linux is up, leaving the wifi and bluetooth without their
> 32.768 kHz reference.
> 
> Select the clock function when the output is prepared, so that it can
> also be given back, and report the output as prepared only when it is
> enabled and on the clock function. The bit is not defined on the other
> variants, so give the RK818 its own clk_ops. Boards that never take the
> clock are unaffected.
> 
> Based on an out-of-tree patch by Martijn Braam & Kamil Trzciński,
> carried by Ondrej Jirman.
> 
> Signed-off-by: Martijn Braam <martijn@brixit.nl>
> Signed-off-by: Rudraksha Gupta <guptarud@gmail.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260824-ppp_connectivity-v2-0-a4b0e11cd62c@gmail.com?part=2


      reply	other threads:[~2026-08-25  5:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25  5:18 [PATCH v2 0/2] Pinephone Pro Connectivity: Adding Modem, Bluetooth, and Wi-Fi Rudraksha Gupta via B4 Relay
2026-08-25  5:18 ` [PATCH v2 1/2] arm64: dts: rockchip: Enable the EG25-G modem on the Pinephone Pro Rudraksha Gupta via B4 Relay
2026-08-25  5:24   ` sashiko-bot
2026-08-25  5:18 ` [PATCH v2 2/2] clk: rk808: Select the clock function of CLK32KOUT2 on the RK818 Rudraksha Gupta via B4 Relay
2026-08-25  5:22   ` sashiko-bot [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=20260825052211.775701F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=guptarud@gmail.com \
    --cc=lee@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mfd@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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