From: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] media: dt-bindings: Add qcom,sm6150-camss
Date: Wed, 24 Dec 2025 13:36:26 +0800 [thread overview]
Message-ID: <26536725-19fe-4aa6-8a33-8e2e39261cd4@oss.qualcomm.com> (raw)
In-Reply-To: <3342fv43qdkmm66jgc63hho2kd3xn65p2fv3tyk3573izlxf7i@hgjsp2kwqyuh>
On 12/24/2025 1:03 PM, Dmitry Baryshkov wrote:
> On Wed, Dec 24, 2025 at 12:31:33PM +0800, Wenmeng Liu wrote:
>>
>>
>> On 12/24/2025 12:21 PM, Dmitry Baryshkov wrote:
>>> On Wed, Dec 24, 2025 at 11:18:02AM +0800, Wenmeng Liu wrote:
>>>>
>>>>
>>>> On 12/23/2025 9:38 PM, Krzysztof Kozlowski wrote:
>>>>> On Mon, Dec 22, 2025 at 04:28:39PM +0800, Wenmeng Liu wrote:
>>>>>> + interconnects:
>>>>>> + maxItems: 4
>>>>>> +
>>>>>> + interconnect-names:
>>>>>> + items:
>>>>>> + - const: ahb
>>>>>> + - const: hf0_mnoc
>>>>>> + - const: hf1_mnoc
>>>>>
>>>>> Same comments as before, do not invent names.
>>>>
>>>> <&mmss_noc MASTER_CAMNOC_HF0 QCOM_ICC_TAG_ALWAYS
>>>> &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,
>>>> <&mmss_noc MASTER_CAMNOC_HF1 QCOM_ICC_TAG_ALWAYS
>>>> &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,
>>>>
>>>> This platform(qcs615) is different from others. It has two types of sf,
>>>> namely sf0 and sf1.
>>>> The same as it is:
>>>> sc7180 sc8180x sdm670 sdm845 sm8150
>>>> Do you have any suggestions about this?
>>>
>>> Which _names_ are used on other platforms? This question is quite clear
>>> from Krzysztof's comment.
>>
>> The platform mentioned above either has no camss ICC node or no support for
>> CAMSS on the upstream, so this is a new one.
>
> I did a quick look for you.
>
> kodiak, lemans, monaco: ahb, hf_0
>
> x1e80100: ahb, hf_mnoc, sf_mnoc, sf_icp_mnoc
> sm8650: ahb, hf_mnoc
> agatti: ahb, hf_mnoc, sf_mnoc
> sm8550: ahb, hf_0_mnoc
>
> sc8280xp: cam_ahb, cam_hf_mnoc, cam_sf_mnoc, cam_sf_icp_mnoc
> sm8250: cam_ahb, cam_hf_0_mnoc, cam_sf_0_mnoc, cam_sf_icp_mnoc
> sdm660: vfe-mem
>
> I'd obviously hope for some unification here. Other than that, we have
> two clean winners: KLM and X Elite+SM8650+Agatti. Yours proposal is
> different from either of the options. In fact, none of the platforms
> have the same _approach_ as yours. Why?
>
Yes, you're right.
But none of the above cases involved having two hf_mnoc simultaneously,
so do you have any good suggestions for handling such a situation?
Thanks,
Wenmeng
next prev parent reply other threads:[~2025-12-24 5:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 8:28 [PATCH v2 0/3] media: qcom: camss: Add sm6150 camss support Wenmeng Liu
2025-12-22 8:28 ` [PATCH v2 1/3] media: dt-bindings: Add qcom,sm6150-camss Wenmeng Liu
2025-12-23 13:38 ` Krzysztof Kozlowski
2025-12-24 3:18 ` Wenmeng Liu
2025-12-24 4:21 ` Dmitry Baryshkov
2025-12-24 4:31 ` Wenmeng Liu
2025-12-24 5:03 ` Dmitry Baryshkov
2025-12-24 5:36 ` Wenmeng Liu [this message]
2025-12-24 6:20 ` Dmitry Baryshkov
2025-12-24 9:46 ` Krzysztof Kozlowski
2025-12-24 10:29 ` Wenmeng Liu
2025-12-24 12:24 ` Dmitry Baryshkov
2025-12-24 9:43 ` Krzysztof Kozlowski
2025-12-22 8:28 ` [PATCH v2 2/3] media: qcom: camss: add support for SM6150 camss Wenmeng Liu
2026-01-12 0:34 ` Bryan O'Donoghue
2026-01-12 8:12 ` Wenmeng Liu
2025-12-22 8:28 ` [PATCH v2 3/3] arm64: dts: qcom: talos: Add camss node Wenmeng Liu
2025-12-23 13:35 ` [PATCH v2 0/3] media: qcom: camss: Add sm6150 camss support Krzysztof Kozlowski
2025-12-24 3:25 ` Wenmeng Liu
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=26536725-19fe-4aa6-8a33-8e2e39261cd4@oss.qualcomm.com \
--to=wenmeng.liu@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--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