All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "David Heidelberg via B4 Relay" <devnull+david.ixit.cz@kernel.org>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH v6 3/8] media: qcom: camss: Prepare CSID for C-PHY support
Date: Wed, 03 Jun 2026 00:03:48 +0000	[thread overview]
Message-ID: <20260603000349.734851F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260603-qcom-cphy-v6-3-e50de0b557a8@ixit.cz>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] State leak: `csid->phy.cphy` is not explicitly reset when linking to the Test Pattern Generator (TPG), leading to stale hardware configuration.
--

commit 0af85d683a316522712652086dfff4934fe24c0c
Author: David Heidelberg <david@ixit.cz>
Subject: media: qcom: camss: Prepare CSID for C-PHY support

Inherit C-PHY information from CSIPHY, so we can configure CSID properly.
CSI2_RX_CFG0_PHY_TYPE_SEL must be set to 1, when C-PHY mode is used.

> diff --git a/drivers/media/platform/qcom/camss/camss-csid.c b/drivers/media/platform/qcom/camss/camss-csid.c
> --- a/drivers/media/platform/qcom/camss/camss-csid.c
> +++ b/drivers/media/platform/qcom/camss/camss-csid.c
> @@ -1291,6 +1291,7 @@ static int csid_link_setup(struct media_entity *entity,
>  
>  			lane_cfg = &csiphy->cfg.csi2->lane_cfg;
>  			csid->phy.lane_cnt = lane_cfg->num_data;
> +			csid->phy.cphy = (lane_cfg->phy_cfg == V4L2_MBUS_CSI2_CPHY);

[Severity: Medium]
Does this leave stale state when linking to the Test Pattern Generator (TPG)
later?

If a C-PHY sensor is linked, csid->phy.cphy is set to true here. If that
sensor is later unlinked and the TPG is linked, the TPG link logic updates
other PHY parameters but does not reset cphy:

        if (sd->grp_id == TPG_GRP_ID) {
                tpg = v4l2_get_subdevdata(sd);
                csid->phy.lane_cnt = tpg->res->lane_cnt;
                csid->phy.csiphy_id = tpg->id;
                csid->phy.lane_assign = csid_get_lane_assign(NULL, csid->phy.lane_cnt);
                csid->tpg_linked = true;
        }

When __csid_configure_rx() is called, it writes this leftover value into
CSI2_RX_CFG0_PHY_TYPE_SEL. Could this cause the TPG stream data to be garbled
by configuring the hardware to expect 3-phase C-PHY encoding instead of D-PHY?

>  			csid->phy.lane_assign = csid_get_lane_assign(lane_cfg, lane_cfg->num_data);
>  			csid->tpg_linked = false;
>  		}

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260603-qcom-cphy-v6-0-e50de0b557a8@ixit.cz?part=3

  reply	other threads:[~2026-06-03  0:03 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 23:30 [PATCH v6 0/8] media: camss: Add support for C-PHY configuration on Qualcomm platforms David Heidelberg via B4 Relay
2026-06-02 23:30 ` David Heidelberg
2026-06-02 23:30 ` [PATCH v6 1/8] media: qcom: camss: csiphy: Introduce PHY configuration David Heidelberg via B4 Relay
2026-06-02 23:30   ` David Heidelberg
2026-06-03 21:34   ` Frank Li
2026-06-02 23:30 ` [PATCH v6 2/8] media: qcom: camss: csiphy-3ph: Use odd bits for configuring C-PHY lanes David Heidelberg via B4 Relay
2026-06-02 23:30   ` David Heidelberg
2026-06-02 23:55   ` sashiko-bot
2026-06-03 21:42   ` Frank Li
2026-06-03 21:57     ` Bryan O'Donoghue
2026-06-04 12:08       ` David Heidelberg
2026-06-02 23:30 ` [PATCH v6 3/8] media: qcom: camss: Prepare CSID for C-PHY support David Heidelberg via B4 Relay
2026-06-02 23:30   ` David Heidelberg
2026-06-03  0:03   ` sashiko-bot [this message]
2026-06-03 21:47   ` Frank Li
2026-06-04 12:34     ` David Heidelberg
2026-06-04 19:07       ` Frank Li
2026-06-05  8:50         ` Bryan O'Donoghue
2026-06-02 23:30 ` [PATCH v6 4/8] media: qcom: camss: Initialize lanes after lane configuration is available David Heidelberg via B4 Relay
2026-06-02 23:30   ` David Heidelberg
2026-06-03  0:13   ` sashiko-bot
2026-06-03 21:49   ` Frank Li
2026-06-02 23:30 ` [PATCH v6 5/8] media: qcom: camss: csiphy-3ph: Add Gen2 v1.1 MIPI CSI-2 C-PHY init David Heidelberg via B4 Relay
2026-06-02 23:30   ` David Heidelberg
2026-06-03  0:26   ` sashiko-bot
2026-06-03 21:53   ` Frank Li
2026-06-05 10:25     ` Bryan O'Donoghue
2026-06-05 14:47       ` Michael Srba
2026-06-05 22:20         ` Bryan O'Donoghue
2026-06-02 23:30 ` [PATCH v6 6/8] media: qcom: camss: csiphy-3ph: Update " David Heidelberg via B4 Relay
2026-06-02 23:30   ` David Heidelberg
2026-06-02 23:30 ` [PATCH v6 7/8] media: qcom: camss: Account for C-PHY when calculating link frequency David Heidelberg via B4 Relay
2026-06-02 23:30   ` David Heidelberg
2026-06-03  0:53   ` sashiko-bot
2026-06-02 23:30 ` [PATCH v6 8/8] media: qcom: camss: Enable C-PHY where available David Heidelberg via B4 Relay
2026-06-02 23:30   ` David Heidelberg
2026-06-03 21:54   ` Frank Li
2026-06-03 10:03 ` [PATCH v6 0/8] media: camss: Add support for C-PHY configuration on Qualcomm platforms Bryan O'Donoghue
2026-06-03 10:17   ` David Heidelberg

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=20260603000349.734851F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=devnull+david.ixit.cz@kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sashiko-reviews@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.