From: Hangxiang Ma <hangxiang.ma@oss.qualcomm.com>
To: bod@kernel.org, sashiko@lists.linux.dev
Cc: conor+dt@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v13 4/5] media: qcom: camss: csid: Add support for CSID gen4
Date: Mon, 1 Jun 2026 16:47:07 +0800 [thread overview]
Message-ID: <83de83e9-ad0e-4aa0-b48a-fa922c560f78@oss.qualcomm.com> (raw)
In-Reply-To: <178018791720.17481.10983668954574740501.b4-reply@b4>
On 5/31/2026 8:38 AM, bod@kernel.org wrote:
>>
>> [ ... ]
>>
>>> +static void __csid_configure_rdi_stream(struct csid_device *csid, u8 enable, u8 port, u8 vc)
>>> +{
>>> + u32 val;
>>> + u8 lane_cnt = csid->phy.lane_cnt;
>>> +
>>> + /* Source pads matching RDI channels on hardware.
>>> + * E.g. Pad 1 -> RDI0, Pad 2 -> RDI1, etc.
>>> + */
>>> + struct v4l2_mbus_framefmt *input_format = &csid->fmt[MSM_CSID_PAD_FIRST_SRC + port];
>>
>> The macro MSM_CSID_MAX_SRC_STREAMS_GEN4 evaluates to 5 for non-lite CSID
>> hardware, meaning the loop index port can reach 4.
>>
>> Since MSM_CSID_PAD_FIRST_SRC is 1, MSM_CSID_PAD_FIRST_SRC + port evaluates
>> to 5.
>
> That's worrying.
>
> Would appreciate some follow-up from patch authors on this one "yes we
> looked no that can't happen" "yes we looked no it can't happen"
>
> Either is acceptable.
It cannot happens as we have limited the vfe_line number to 3 due to
camss framework limitation.
Best regards,
Hangxiang
next prev parent reply other threads:[~2026-06-01 8:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FXDAuI5m6Enkr_1xXCRtdAt_nLft5hGS75Kmuwi4PN4Rv4Z-d631VEvnGqL3Vygade8Z6Bnqwllnv8tU8oqH_g==@protonmail.internalid>
2026-05-08 8:05 ` [PATCH v13 0/5] media: qcom: camss: Add Kaanapali support Hangxiang Ma
2026-05-08 8:05 ` [PATCH v13 1/5] media: dt-bindings: Add CAMSS device for Kaanapali Hangxiang Ma
2026-06-02 22:13 ` Vladimir Zapolskiy
2026-05-08 8:05 ` [PATCH v13 2/5] media: qcom: camss: Add Kaanapali compatible camss driver Hangxiang Ma
2026-05-08 20:33 ` sashiko-bot
2026-06-02 22:14 ` Vladimir Zapolskiy
2026-05-08 8:05 ` [PATCH v13 3/5] media: qcom: camss: csiphy: Add support for v2.4.0 two-phase CSIPHY Hangxiang Ma
2026-06-02 22:15 ` Vladimir Zapolskiy
2026-05-08 8:05 ` [PATCH v13 4/5] media: qcom: camss: csid: Add support for CSID gen4 Hangxiang Ma
2026-05-08 21:22 ` sashiko-bot
2026-05-31 0:38 ` bod
2026-06-01 8:47 ` Hangxiang Ma [this message]
2026-05-31 0:30 ` bod
2026-05-08 8:05 ` [PATCH v13 5/5] media: qcom: camss: vfe: Add support for VFE gen4 Hangxiang Ma
2026-05-08 21:56 ` sashiko-bot
2026-05-31 11:29 ` [PATCH v13 0/5] media: qcom: camss: Add Kaanapali 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=83de83e9-ad0e-4aa0-b48a-fa922c560f78@oss.qualcomm.com \
--to=hangxiang.ma@oss.qualcomm.com \
--cc=bod@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko@lists.linux.dev \
/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).