From: Krzysztof Kozlowski <krzk@kernel.org>
To: Hangxiang Ma <hangxiang.ma@oss.qualcomm.com>
Cc: Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
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>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
jeyaprakash.soundrapandian@oss.qualcomm.com,
Vijay Kumar Tumati <vijay.tumati@oss.qualcomm.com>
Subject: Re: [PATCH RESEND v2 1/5] media: dt-bindings: Add CAMSS device for SM8750
Date: Tue, 20 Jan 2026 10:35:42 +0100 [thread overview]
Message-ID: <20260120-kickass-taipan-from-hyperborea-e53ea6@quoll> (raw)
In-Reply-To: <20260119-add-support-for-camss-on-sm8750-v2-1-3e06583a0a81@oss.qualcomm.com>
On Mon, Jan 19, 2026 at 10:42:51PM -0800, Hangxiang Ma wrote:
> + - description: Registers for RT CDM 1
> + - description: Registers for RT CDM 2
> + - description: Registers for RT CDM 3
> + - description: Registers for RT CDM 4
> + - description: Registers for TPG 0
> + - description: Registers for TPG 1
> + - description: Registers for TPG 2
> +
> + reg-names:
> + items:
> + - const: csid0
> + - const: csid1
> + - const: csid2
> + - const: csid_lite0
> + - const: csid_lite1
> + - const: csiphy0
> + - const: csiphy1
> + - const: csiphy2
> + - const: csiphy3
> + - const: csiphy4
> + - const: csiphy5
Same comment as last time - nothing got resolved, nothing got concluded.
And before you claim without supporting arguments "we are not blocking"
let me clarify: yes, you are blocked, because I am not taking bindings
which are known to be incomplete, not finished and already being
changed/worked on.
> + - const: gcc_axi_hf
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-20 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 6:42 [PATCH RESEND v2 0/5] media: qcom: camss: Add SM8750 support Hangxiang Ma
2026-01-20 6:42 ` [PATCH RESEND v2 1/5] media: dt-bindings: Add CAMSS device for SM8750 Hangxiang Ma
2026-01-20 9:35 ` Krzysztof Kozlowski [this message]
2026-01-20 18:58 ` Vijay Kumar Tumati
2026-01-20 21:28 ` Bryan O'Donoghue
2026-02-18 20:08 ` Krzysztof Kozlowski
2026-02-19 0:50 ` Bryan O'Donoghue
2026-02-19 1:08 ` Vijay Kumar Tumati
2026-02-19 13:09 ` Bryan O'Donoghue
2026-02-26 9:59 ` Krzysztof Kozlowski
2026-02-26 10:08 ` Bryan O'Donoghue
2026-01-20 6:42 ` [PATCH RESEND v2 2/5] media: qcom: camss: Add SM8750 compatible camss driver Hangxiang Ma
2026-01-20 6:42 ` [PATCH RESEND v2 3/5] media: qcom: camss: csiphy: Add support for v2.3.0 two-phase CSIPHY Hangxiang Ma
2026-01-20 6:42 ` [PATCH RESEND v2 4/5] media: qcom: camss: csid: Add support for CSID 980 Hangxiang Ma
2026-01-20 6:42 ` [PATCH RESEND v2 5/5] media: qcom: camss: vfe: Add support for VFE 980 Hangxiang Ma
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=20260120-kickass-taipan-from-hyperborea-e53ea6@quoll \
--to=krzk@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hangxiang.ma@oss.qualcomm.com \
--cc=jeyaprakash.soundrapandian@oss.qualcomm.com \
--cc=krzk+dt@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=vijay.tumati@oss.qualcomm.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