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 3/4] clk: qcom: Add Audio Core clock controller support on Qualcomm Shikra SoC
Date: Mon, 29 Jun 2026 10:49:41 +0530 [thread overview]
Message-ID: <78abffc7-3b3b-4fed-9d9b-cfa9fa3778cc@oss.qualcomm.com> (raw)
In-Reply-To: <191c4b05-7d66-4338-8321-ebc593379f73@oss.qualcomm.com>
On 11-06-2026 04:57 pm, Konrad Dybcio wrote:
> On 6/5/26 1:26 PM, Imran Shaik wrote:
>> Add support for Audio Core Clock Controller (AUDIOCORECC) on Qualcomm
>> Shikra SoC. The AUDIOCORECC clocks and resets support differs based on
>> Audio subsystem enablement. In the CQM variant, both clocks and resets
>> are required as Audio is on APPS, while in the CQS variant only reset
>> control is required since Audio is handled on Modem. Handle these
>> requirements using variant specific compatibles.
>>
>> Signed-off-by: Imran Shaik <imran.shaik@oss.qualcomm.com>
>> ---
>
> [...]
>
>> +static const struct qcom_reset_map audio_core_cc_shikra_resets[] = {
>> + [AUDIO_CORE_CSR_RX_SWR_CGCR] = { 0x1c },
>> + [AUDIO_CORE_CSR_TX_SWR_CGCR] = { 0x30 },
>
My bad, this also should be controlling the BIT(1) only from SW side,
similar to existing drivers. I will update in the next series.
> So these are not "real resets", but for the sake of existing art, we
> can keep pretending they are
>
> bit 1 is HW_CTL (1->hw controlled) and bit 0 is taken into account only
> if 1 is cleared
>
> existing drivers toggle the HW_CTRL bit (meaning it's an
> maybe-on/surely-on switch rather than off/on).. do we need to rectify
> that somehow?
>
No changes are needed to the existing logic, as Audio SW only needs to
control the HW_CTL bit.
By default (PoR), HW_CTL is asserted, so the CGCRs are controlled by
hardware. For the audio use case, where HW gating isn’t required,
software de-asserts HW_CTL, after which control shifts to bit 0 (set to
1 by default).
Thanks,
Imran
next 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 [this message]
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
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=78abffc7-3b3b-4fed-9d9b-cfa9fa3778cc@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