From: "Rob Herring (Arm)" <robh@kernel.org>
To: Sarath Ganapathiraju <sarath.ganapathiraju@oss.qualcomm.com>
Cc: andersson@kernel.org, bmasney+clk@redhat.com,
conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
sboyd@kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
prasad.kumpatla@oss.qualcomm.com, jbrunet+clk@baylibre.com,
srinivas.kandagatla@oss.qualcomm.com, krzk+dt@kernel.org,
abelvesa@kernel.org
Subject: Re: [PATCH v9 1/2] dt-bindings: clock: qcom: Add LPASS VA CSR HeartBeat pulse clock
Date: Mon, 28 Sep 2026 16:13:46 -0500 [thread overview]
Message-ID: <179063002588.652413.6187183335984083646.robh@kernel.org> (raw)
In-Reply-To: <20260928-master-v9-1-2277f09f9a09@oss.qualcomm.com>
On Mon, 28 Sep 2026 21:27:38 +0530, Sarath Ganapathiraju wrote:
> Add a binding for the Qualcomm LPASS VA CSR rate generator node that
> exposes the lpass_heartbeat_pulse clock on Hawi.
>
> The HeartBeat Pulse, also known as RateGen Pulse, synchronizes the
> start of DMAs and Codec Interfaces for the audio usecase and can serve
> as a periodic wakeup source for the DSP.
>
> Require the LPASS LPR and audio vote clocks to access VA CSR register
> space safely.
>
> Signed-off-by: Sarath Ganapathiraju <sarath.ganapathiraju@oss.qualcomm.com>
> ---
> .../bindings/clock/qcom,hawi-lpass-va-csr.yaml | 62 ++++++++++++++++++++++
> 1 file changed, 62 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-09-28 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 15:57 [PATCH v9 0/2] Add LPASS VA CSR HeartBeat pulse clock support Sarath Ganapathiraju via B4 Relay
2026-09-28 15:57 ` [PATCH v9 1/2] dt-bindings: clock: qcom: Add LPASS VA CSR HeartBeat pulse clock Sarath Ganapathiraju via B4 Relay
2026-09-28 21:13 ` Rob Herring (Arm) [this message]
2026-09-28 15:57 ` [PATCH v9 2/2] clk: qcom: Add LPASS VA CSR heartbeat " Sarath Ganapathiraju via B4 Relay
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=179063002588.652413.6187183335984083646.robh@kernel.org \
--to=robh@kernel.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prasad.kumpatla@oss.qualcomm.com \
--cc=sarath.ganapathiraju@oss.qualcomm.com \
--cc=sboyd@kernel.org \
--cc=srinivas.kandagatla@oss.qualcomm.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®