[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <72b61199-bb70-4965-9ca9-f21966195f60@quicinc.com>
Date: Fri, 16 May 2025 18:32:32 +0800
From: Wenmeng Liu <quic_wenmliu@...cinc.com>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
Konrad Dybcio
<konrad.dybcio@....qualcomm.com>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>
CC: <linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Depeng Shao <quic_depengs@...cinc.com>
Subject: Re: [PATCH] arm64: dts: qcom: sm8550: Add support for camss
On 2025/5/16 18:15, Bryan O'Donoghue wrote:
> On 16/05/2025 08:34, Wenmeng Liu wrote:
>>> This should be 689 yes
>>>
>>> ---
>>> bod
>>
>> Hi Bryan,Konrad,
>>
>> I confirmed that the value is 688 instead of 689. The documentation
>> incorrectly listed it as 689. To CC linux-media, I have resent the patch:
>> https://lore.kernel.org/linux-arm-msm/20250516072707.388332-1-
>> quic_wenmliu@...cinc.com/
>
> Do you mean the documentation in the kernel or the documentation inside
> of qcom ?
>
> I checked the internal silicon definition, I think Konrad did also.
>
> Which documentation do you mean here ?
>
> ---
> bod
I mean is the ipcat documentation.
And if configured to 689, the interrupt will fail to request:
irq:irq: type mismatch, failed to map hwirq-721 for
interrupt-controller@...00000!
According the mobile configuration, this value should be 688.
Thanks,
Wenmeng
Powered by blists - more mailing lists