From: sashiko-bot@kernel.org
To: "Sarath Ganapathiraju" <sarath.ganapathiraju@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/2] clk: qcom: Add LPASS VA CSR heartbeat pulse clock
Date: Wed, 05 Aug 2026 10:43:46 +0000 [thread overview]
Message-ID: <20260805104348.BA1041F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260805-master-20260805-sync-v4-2-dfbcbf427c2c@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing architecture dependencies in `QCOM_CLK_LPASS_HEARTBEAT_PULSE` Kconfig entry.
--
--- Patch [2]: [PATCH v4 2/2] clk: qcom: Add LPASS VA CSR heartbeat pulse clock ---
commit f03b41ee3ba8e25df484407c379a0d86e064e1b4
Author: Sarath Ganapathiraju <sarath.ganapathiraju@oss.qualcomm.com>
clk: qcom: Add LPASS VA CSR heartbeat pulse clock
This commit introduces the LPASS VA CSR driver to model the rate generator
as a clock provider. It allows the HeartBeat Pulse to be enabled and
disabled automatically alongside other clocks during runtime PM operations.
> diff --git a/drivers/clk/qcom/Kconfig b/drivers/clk/qcom/Kconfig
> index d1fc9bf87126b..d9a4ceb1d3a03 100644
> --- a/drivers/clk/qcom/Kconfig
> +++ b/drivers/clk/qcom/Kconfig
> @@ -2040,6 +2040,18 @@ config CLK_GFM_LPASS_SM8250
> Support for the Glitch Free Mux (GFM) Low power audio
> subsystem (LPASS) clocks found on SM8250 SoCs.
>
> +config QCOM_CLK_LPASS_HEARTBEAT_PULSE
> + tristate "Qualcomm LPASS VA CSR heartbeat pulse clock provider"
> + depends on COMMON_CLK
> + select REGMAP_MMIO
[Severity: Low]
Should this configuration depend on ARCH_QCOM or COMPILE_TEST?
Without architecture constraints, this SoC-specific clock driver is exposed
in the configuration menu for all architectures. Adding a dependency on
ARCH_QCOM || COMPILE_TEST would prevent this menuconfig pollution.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260805-master-20260805-sync-v4-0-dfbcbf427c2c@oss.qualcomm.com?part=2
prev parent reply other threads:[~2026-08-05 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 10:33 [PATCH v4 0/2] Add LPASS VA CSR HeartBeat pulse clock support Sarath Ganapathiraju via B4 Relay
2026-08-05 10:33 ` [PATCH v4 1/2] dt-bindings: clock: qcom: Add LPASS VA CSR HeartBeat pulse clock Sarath Ganapathiraju via B4 Relay
2026-08-05 10:33 ` [PATCH v4 2/2] clk: qcom: Add LPASS VA CSR heartbeat " Sarath Ganapathiraju via B4 Relay
2026-08-05 10:43 ` 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=20260805104348.BA1041F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sarath.ganapathiraju@oss.qualcomm.com \
--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