From: Imran Shaik <imran.shaik@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Ajit Pandey <ajit.pandey@oss.qualcomm.com>,
Taniya Das <taniya.das@oss.qualcomm.com>,
Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: qcom: shikra: Add support for AudioCoreCC node
Date: Mon, 29 Jun 2026 10:50:50 +0530 [thread overview]
Message-ID: <4980d925-ec32-4632-a377-d65b9ac1d152@oss.qualcomm.com> (raw)
In-Reply-To: <b3a0fb12-5595-43ba-b552-cbf06d1f9260@oss.qualcomm.com>
On 11-06-2026 04:55 pm, Konrad Dybcio wrote:
> On 6/5/26 1:26 PM, Imran Shaik wrote:
>> Add support for Audio Core Clock Controller (AudioCoreCC) node on Qualcomm
>> Shikra SoC. The CQM variant requires both clock and reset support, while
>> the CQS variant requires only reset support. Update the respective device
>> tree variants to enable and override the node as per variant requirements.
>>
>> Signed-off-by: Imran Shaik <imran.shaik@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts | 4 ++++
>> arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts | 5 +++++
>> arch/arm64/boot/dts/qcom/shikra.dtsi | 13 +++++++++++++
>> 3 files changed, 22 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts b/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
>> index 0a52ab9b7a4c34d371f5ac23efe59d1c9d2723f4..0883c480bfbc80d7bead966b9ba932dee8a77bbf 100644
>> --- a/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
>> +++ b/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
>> @@ -23,6 +23,10 @@ chosen {
>> };
>> };
>>
>> +&audiocorecc {
>> + status = "okay";
>> +};
>> +
>> &sdhc_1 {
>> vmmc-supply = <&pm4125_l20>;
>> vqmmc-supply = <&pm4125_l14>;
>> diff --git a/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts b/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts
>> index b3f19a64d7aed3121ef092df684b19a4de39b497..b5e3d573868a836ad5e5e8eb3024cb5fb71dbb4e 100644
>> --- a/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts
>> +++ b/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts
>> @@ -23,6 +23,11 @@ chosen {
>> };
>> };
>>
>> +&audiocorecc {
>> + compatible = "qcom,shikra-cqs-audiocorecc";
>> + status = "okay";
>> +};
>> +
>> &sdhc_1 {
>> vmmc-supply = <&pm4125_l20>;
>> vqmmc-supply = <&pm4125_l14>;
>> diff --git a/arch/arm64/boot/dts/qcom/shikra.dtsi b/arch/arm64/boot/dts/qcom/shikra.dtsi
>> index a4334d99c1f35ee851ca8266ec37d4a200a07ee5..f15757d52af04d8cb5540354a239127cb0d174a3 100644
>> --- a/arch/arm64/boot/dts/qcom/shikra.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/shikra.dtsi
>> @@ -4,6 +4,7 @@
>> */
>>
>> #include <dt-bindings/clock/qcom,rpmcc.h>
>> +#include <dt-bindings/clock/qcom,shikra-audiocorecc.h>
>> #include <dt-bindings/clock/qcom,shikra-gcc.h>
>> #include <dt-bindings/interconnect/qcom,icc.h>
>> #include <dt-bindings/interconnect/qcom,rpm-icc.h>
>> @@ -640,6 +641,18 @@ &clk_virt SLAVE_QUP_CORE_0 RPM_ALWAYS_TAG>,
>> };
>> };
>>
>> + audiocorecc: clock-controller@a0a0000 {
>> + compatible = "qcom,shikra-cqm-audiocorecc";
>> + reg = <0x0 0x0a0a0000 0x0 0x10000>,
>
> This is called AUDIO_CORE_CC where seemingly all the clocks live
>
>> + <0x0 0x0a0b4000 0x0 0x1000>;
>
> and this is called AUDIO_CORE_CSR where seemingly all the resets live
>
> so it would make sense to split them
Yes, the clocks and resets reside in different register spaces, I will
split them into two different nodes as suggested. This will help to
handle the CQM/CQS variants requirements more cleanly.
Thanks,
Imran
prev parent reply other threads:[~2026-06-29 5:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 11:26 [PATCH 0/4] clk: qcom: Add Audio Core clock controller support on Qualcomm Shikra SoC Imran Shaik
2026-06-05 11:26 ` [PATCH 1/4] clk: qcom: common: Register reset controller only when resets are present Imran Shaik
2026-06-05 11:26 ` [PATCH 2/4] dt-bindings: clock: qcom: Add Qualcomm Shikra Audio Core Clock Controller Imran Shaik
2026-06-07 11:18 ` Dmitry Baryshkov
2026-06-29 5:21 ` Imran Shaik
2026-06-08 10:49 ` Krzysztof Kozlowski
2026-06-29 5:28 ` Imran Shaik
2026-06-05 11:26 ` [PATCH 3/4] clk: qcom: Add Audio Core clock controller support on Qualcomm Shikra SoC Imran Shaik
2026-06-11 11:22 ` Konrad Dybcio
2026-06-11 11:27 ` Konrad Dybcio
2026-06-29 5:19 ` Imran Shaik
2026-06-05 11:26 ` [PATCH 4/4] arm64: dts: qcom: shikra: Add support for AudioCoreCC node Imran Shaik
2026-06-11 11:25 ` Konrad Dybcio
2026-06-29 5:20 ` Imran Shaik [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=4980d925-ec32-4632-a377-d65b9ac1d152@oss.qualcomm.com \
--to=imran.shaik@oss.qualcomm.com \
--cc=ajit.pandey@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--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=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=taniya.das@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