devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Wenmeng Liu <quic_wenmliu@quicinc.com>,
	Konrad Dybcio <konrad.dybcio@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>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Depeng Shao <quic_depengs@quicinc.com>
Subject: Re: [PATCH] arm64: dts: qcom: sm8550: Add support for camss
Date: Fri, 16 May 2025 11:15:49 +0100	[thread overview]
Message-ID: <36f02ed8-b440-4760-8d08-b633406ce92a@linaro.org> (raw)
In-Reply-To: <db059233-523d-420b-81a7-73b02beef4d1@quicinc.com>

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@quicinc.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

  reply	other threads:[~2025-05-16 10:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15  7:38 [PATCH] arm64: dts: qcom: sm8550: Add support for camss Wenmeng Liu
2025-04-30 11:11 ` Konrad Dybcio
2025-05-01  1:15   ` Bryan O'Donoghue
2025-05-16  7:34     ` Wenmeng Liu
2025-05-16 10:15       ` Bryan O'Donoghue [this message]
2025-05-16 10:32         ` Wenmeng Liu
2025-05-16 10:41           ` Bryan O'Donoghue

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=36f02ed8-b440-4760-8d08-b633406ce92a@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@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_depengs@quicinc.com \
    --cc=quic_wenmliu@quicinc.com \
    --cc=robh@kernel.org \
    --cc=vladimir.zapolskiy@linaro.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;
as well as URLs for NNTP newsgroup(s).