From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Loic Poulain <loic.poulain@oss.qualcomm.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: andersson@kernel.org, konradybcio@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: qcm2290: Add CCI node
Date: Wed, 9 Apr 2025 20:39:05 +0200 [thread overview]
Message-ID: <170e4c9a-bdf4-44f7-9dd1-9eed31fa27db@oss.qualcomm.com> (raw)
In-Reply-To: <CAFEp6-2kamY6m_vzE0gMi-QKCRYf42RjMd7f2ud6bte=aL9mRA@mail.gmail.com>
On 4/7/25 4:56 PM, Loic Poulain wrote:
> Hi Bryan,
>
>
> On Fri, Apr 4, 2025 at 2:10 PM Bryan O'Donoghue
> <bryan.odonoghue@linaro.org> wrote:
>>
>> On 03/04/2025 11:22, Loic Poulain wrote:
>>> Add Camera Control Interface (CCI), supporting two I2C masters.
>>>
>>> Signed-off-by: Loic Poulain <loic.poulain@oss.qualcomm.com>
>>> ---
>>> v2: Reorder commits; Update dts properties order and style
>>> v3: No change for this patch
>>>
>>> arch/arm64/boot/dts/qcom/qcm2290.dtsi | 50 +++++++++++++++++++++++++++
>>> 1 file changed, 50 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/qcom/qcm2290.dtsi b/arch/arm64/boot/dts/qcom/qcm2290.dtsi
>>> index 7fb5de92bc4c..43fcb4f40a8c 100644
>>> --- a/arch/arm64/boot/dts/qcom/qcm2290.dtsi
>>> +++ b/arch/arm64/boot/dts/qcom/qcm2290.dtsi
>>> @@ -557,6 +557,20 @@ qup_uart4_default: qup-uart4-default-state {
>>> bias-disable;
>>> };
>>>
>>> + cci0_default: cci0-default-state {
>>> + pins = "gpio22", "gpio23";
>>> + function = "cci_i2c";
>>> + drive-strength = <2>;
>>> + bias-disable;
>>> + };
>>> +
>>> + cci1_default: cci1-default-state {
>>> + pins = "gpio29", "gpio30";
>>> + function = "cci_i2c";
>>> + drive-strength = <2>;
>>> + bias-disable;
>>> + };
>>> +
>>> sdc1_state_on: sdc1-on-state {
>>> clk-pins {
>>> pins = "sdc1_clk";
>>> @@ -1603,6 +1617,42 @@ adreno_smmu: iommu@59a0000 {
>>> #iommu-cells = <2>;
>>> };
>>>
>>> + cci: cci@5c1b000 {
>>> + compatible = "qcom,qcm2290-cci", "qcom,msm8996-cci";
>>> + reg = <0x0 0x5c1b000 0x0 0x1000>;
>>> +
>>> + interrupts = <GIC_SPI 206 IRQ_TYPE_EDGE_RISING>;
>>> +
>>> + clocks = <&gcc GCC_CAMSS_TOP_AHB_CLK>, <&gcc GCC_CAMSS_CCI_0_CLK>;
>>> + clock-names = "camss_top_ahb", "cci";
>>
>> do you not need an axi clock GCC_CAMSS_AXI_CLK ?
>
> AFAIU AXI is not involved for CCI.
I'm not able to infer that from statically provided infromation, try
forcefully shutting the clock down (both the branch and _SRC) and
poking at the CCI
Konrad
next prev parent reply other threads:[~2025-04-09 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 10:22 [PATCH v3 1/2] dt-bindings: i2c: qcom-cci: Document QCM2290 compatible Loic Poulain
2025-04-03 10:22 ` [PATCH v3 2/2] arm64: dts: qcom: qcm2290: Add CCI node Loic Poulain
2025-04-04 12:10 ` Bryan O'Donoghue
2025-04-07 14:56 ` Loic Poulain
2025-04-09 18:39 ` Konrad Dybcio [this message]
2025-04-11 8:02 ` Loic Poulain
2025-04-11 19:15 ` Konrad Dybcio
2025-04-08 9:39 ` Bryan O'Donoghue
2025-04-11 19:19 ` Konrad Dybcio
2025-04-11 19:19 ` [PATCH v3 1/2] dt-bindings: i2c: qcom-cci: Document QCM2290 compatible Konrad Dybcio
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=170e4c9a-bdf4-44f7-9dd1-9eed31fa27db@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.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