From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
vincent.knecht@mailoo.org, Robert Foss <rfoss@kernel.org>,
Todor Tomov <todor.too@gmail.com>,
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>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
"André Apitzsch" <git@apitzsch.eu>,
phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v5 3/4] media: dt-bindings: Add qcom,msm8939-camss
Date: Thu, 26 Jun 2025 12:41:06 +0100 [thread overview]
Message-ID: <8c83b5c1-b7ca-4fc8-9246-a950c356214c@linaro.org> (raw)
In-Reply-To: <ea5d7622-ef9d-4bfc-af64-87bd19664333@linaro.org>
On 26/06/2025 12:17, Vladimir Zapolskiy wrote:
> What's about MSM8953 then?
Should be fixed up to match 8916. We don't have an upstream user and we,
I, did the wrong thing.
> Please see commit c830aff08d51 ("media: dt-bindings: Add qcom,msm8953-
> camss").
>
>> x1e has a particular order if a new device x1e+1 comes along with a new
>> register then
>>
>
>>
>> I think I personally haven't understood what was meant by "devices of a
>> class" but its clearer now.
>>
>
> And I still didn't get it, how to read this "devices of a class"?
>
> In particular why is MSM8939 a device of MSM8916 class and MSM8953 is
> not?
>
> For sake of simplicity I list only accepted CAMSS dt bindings:
>
> qcom,msm8916-camss.yaml
> qcom,msm8953-camss.yaml
> qcom,msm8996-camss.yaml
> qcom,sc7280-camss.yaml
> qcom,sc8280xp-camss.yaml
> qcom,sdm660-camss.yaml
> qcom,sdm670-camss.yaml
> qcom,sdm845-camss.yaml
> qcom,sm8250-camss.yaml
> qcom,sm8550-camss.yaml
> qcom,x1e80100-camss.yaml
I mean some old commits in Linux wouldn't make it through the
upstreaming process now.
8953 is not right and can be changed.
8250, 845 may have bindings we wouldn't accept now but they have users
so we live with them.
> I kindly ask to select a number of class defining IPs from the list,
> so that all next ones will derive from those only, and not from
> "another class". It's a task for a DT maintainer I presume.
>
> Before completing this and getting a common understanding all next
> work to provide CAMSS suppor for new platforms is not directed by
> any policy, because the policy "do as it's been done before" is
> applied inconsistently.
>
I think I personally am clear on the rule from the DT people, even if I
may not get it right on subsequient submissions.
The sort order thing is a red herring, in simple terms. We should be
consistent in device classes.
For example TITAN 680 and 690 should look pretty similar, TITAN 340 and
990 probably can have greater divergence.
Either way the sort order thing is a dead end, anything upstream on that
basis like x1e is probably fine because it is of its particular class of
device.
8953 and 8939 should match their device class of 8916.
---
bod
next prev parent reply other threads:[~2025-06-26 11:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 9:33 [PATCH v5 0/4] CAMSS support for MSM8939 Vincent Knecht via B4 Relay
2025-06-13 9:33 ` [PATCH v5 1/4] media: qcom: camss: vfe: Add VBIF setting support Vincent Knecht via B4 Relay
2025-06-13 9:33 ` [PATCH v5 2/4] media: qcom: camss: Add support for MSM8939 Vincent Knecht via B4 Relay
2025-06-26 10:56 ` Vladimir Zapolskiy
2025-06-13 9:33 ` [PATCH v5 3/4] media: dt-bindings: Add qcom,msm8939-camss Vincent Knecht via B4 Relay
2025-06-13 11:42 ` Bryan O'Donoghue
2025-06-13 16:38 ` Vladimir Zapolskiy
2025-06-26 10:00 ` Krzysztof Kozlowski
2025-06-26 10:19 ` Bryan O'Donoghue
2025-06-26 10:28 ` Krzysztof Kozlowski
2025-06-26 10:48 ` Bryan O'Donoghue
2025-06-26 11:17 ` Vladimir Zapolskiy
2025-06-26 11:41 ` Bryan O'Donoghue [this message]
2025-06-26 10:02 ` Krzysztof Kozlowski
2025-06-26 11:17 ` Bryan O'Donoghue
2025-06-13 9:33 ` [PATCH v5 4/4] arm64: dts: qcom: msm8939: Add camss and cci Vincent Knecht via B4 Relay
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=8c83b5c1-b7ca-4fc8-9246-a950c356214c@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@apitzsch.eu \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.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=phone-devel@vger.kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vincent.knecht@mailoo.org \
--cc=vladimir.zapolskiy@linaro.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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
all inboxes | Powered by JetHome®