From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jie Gan <quic_jiegan@quicinc.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Jie Gan <jie.gan@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Tingwei Zhang <quic_tingweiz@quicinc.com>,
Jinlong Mao <quic_jinlmao@quicinc.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: qcs615: disable the CTI device of the camera block
Date: Tue, 27 May 2025 12:41:14 +0200 [thread overview]
Message-ID: <1fef810c-47fe-4f6d-95bc-0d72dbd63bf0@oss.qualcomm.com> (raw)
In-Reply-To: <9a156925-cf7b-4d2e-88a8-fdfed5528553@quicinc.com>
On 5/27/25 12:32 PM, Jie Gan wrote:
>
>
> On 5/27/2025 6:23 PM, Konrad Dybcio wrote:
>> On 5/27/25 3:52 AM, Jie Gan wrote:
>>> Disable the CTI device of the camera block to prevent potential NoC errors
>>> during AMBA bus device matching.
>>>
>>> The clocks for the Qualcomm Debug Subsystem (QDSS) are managed by aoss_qmp
>>> through a mailbox. However, the camera block resides outside the AP domain,
>>> meaning its QDSS clock cannot be controlled via aoss_qmp.
>>
>> Which clock drives it then?
>
> It's qcom,aoss-qmp.
>
> clk_prepare->qmp_qdss_clk_prepare
> https://elixir.bootlin.com/linux/v6.15-rc7/source/drivers/soc/qcom/qcom_aoss.c#L280
I'm confused about this part:
> However, the camera block resides outside the AP domain,
> meaning its QDSS clock cannot be controlled via aoss_qmp.
Do we need to poke the QMP of another DRV?
Konrad
next prev parent reply other threads:[~2025-05-27 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 1:52 [PATCH] arm64: dts: qcom: qcs615: disable the CTI device of the camera block Jie Gan
2025-05-27 10:23 ` Konrad Dybcio
2025-05-27 10:32 ` Jie Gan
2025-05-27 10:41 ` Konrad Dybcio [this message]
2025-05-28 3:02 ` Jie Gan
2025-05-30 23:05 ` Konrad Dybcio
2025-06-03 3:17 ` Jie Gan
2025-06-10 13:24 ` Konrad Dybcio
2025-06-11 1:05 ` Jie Gan
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=1fef810c-47fe-4f6d-95bc-0d72dbd63bf0@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jie.gan@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jiegan@quicinc.com \
--cc=quic_jinlmao@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=robh@kernel.org \
/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