From: Shuai Liu <847807867@qq.com>
To: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org
Cc: Shuai Liu <847807867@qq.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Hangxiang Ma <hangxiang.ma@oss.qualcomm.com>,
Qianhui Xu <xiaqinghuan@mail.ustc.edu.cn>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/9] media: camss: csid: add the 980 generation
Date: Thu, 29 Oct 2026 15:54:03 +0800 [thread overview]
Message-ID: <tencent_E9EEF3D2AF2C6DF28E4DC1B855625913D908@qq.com> (raw)
In-Reply-To: <20261028034105.326535-5-xiaqinghuan@mail.ustc.edu.cn>
Hi Qianhui,
The csid-980 register map and RDI configuration itself look sane to me
(the vc=0 stream programming matches what gen2/gen3 already do, and the
split RUP/AUP handling for the full variant is clearly commented).
> Only the register map, the RDI stream configuration and the
> buffer-done reporting are described here; frame start reporting is
> added on top of it by a separate change.
The commit message does not match the patch content, though. As
posted, this patch touches six files, not three:
1. drivers/media/platform/qcom/camss/camss-csiphy-3ph-1-0.c is modified
to flip the four SKEW_CAL data bytes (0x005c and per-lane copies)
from 0x54 to 0x00. That is a correction to patch 2/9 and belongs
there - patch 2 should simply program the intended value, otherwise
the series carries a value its own commit message calls wrong.
2. camss-vfe.c and camss-vfe.h carry groundwork for patches 5/9 and
8/9, none of it described by this commit message:
- the v4l2-event.h include and the hoisting of `line` plus the new
`state` variable in vfe_buf_done() (needed by 5/9);
- the new reg_update_after_csid_config flag in struct
vfe_subdev_resources and the corresponding gating of the
reg_update() call in vfe_enable_output_v2();
- the CAMSS_8750 cases in vfe_src_pad_code() and
vfe_bpl_align_rdi(), and the extern declaration of
vfe_ops_gen4 (all needed by 8/9).
Please fold the csiphy fix into patch 2, the vfe_buf_done/event
groundwork into patch 5, and the gen4 enablement into patch 8 (or
describe the split here if you prefer to keep it), so that each patch
stands on its own.
Thanks,
Shuai Liu
(This review was prepared with the assistance of an AI coding tool;
all findings were verified against the patched source.)
next prev parent reply other threads:[~2026-10-29 7:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 3:40 [PATCH 0/9] media: camss: add SM8750 support Qianhui Xu
2026-10-28 3:40 ` [PATCH 1/9] dt-bindings: media: add the Qualcomm SM8750 camera subsystem Qianhui Xu
2026-10-28 3:40 ` [PATCH 2/9] media: camss: csiphy: add CSIPHY 2.4.0 lane settings for SM8750 Qianhui Xu
2026-10-29 7:53 ` Shuai Liu
2026-10-28 3:40 ` [PATCH 3/9] media: camss: csid: unwind the power-on path through a single error label Qianhui Xu
2026-10-28 3:41 ` [PATCH 4/9] media: camss: csid: add the 980 generation Qianhui Xu
2026-10-29 7:54 ` Shuai Liu [this message]
2026-10-28 3:41 ` [PATCH 5/9] media: camss: csid: report frame starts from CSID Qianhui Xu
2026-10-28 3:41 ` [PATCH 6/9] media: camss: video: check that a buffer is DMA contiguous and add a prepare hook Qianhui Xu
2026-10-28 3:41 ` [PATCH 7/9] media: camss: video: stop the subdevices already started when a start fails Qianhui Xu
2026-10-28 3:41 ` [PATCH 8/9] media: camss: vfe: add the gen4 block and SM8750 camera subsystem Qianhui Xu
2026-10-29 7:54 ` Shuai Liu
2026-10-28 3:41 ` [PATCH 9/9] arm64: dts: qcom: sm8750: add the " Qianhui Xu
2026-10-29 7:54 ` Shuai Liu
2026-10-29 9:37 ` [PATCH 0/9] media: camss: add SM8750 support 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=tencent_E9EEF3D2AF2C6DF28E4DC1B855625913D908@qq.com \
--to=847807867@qq.com \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hangxiang.ma@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=vladimir.zapolskiy@linaro.org \
--cc=xiaqinghuan@mail.ustc.edu.cn \
/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®