From: Bryan O'Donoghue <bod@kernel.org>
To: Oleg Keri <okerixx@gmail.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Nihal Kumar Gupta <nihal.gupta@oss.qualcomm.com>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v13 3/5] media: qcom: camss: Add support for PHY API devices
Date: Wed, 16 Sep 2026 15:43:18 +0100 [thread overview]
Message-ID: <b9693892-d0d3-49aa-8fb8-21da12f6eadc@kernel.org> (raw)
In-Reply-To: <178956537382.2699.6279926603215472320@gmail.com>
On 16/09/2026 14:29, Oleg Keri wrote:
> Hi Bryan,
>
> On Tue, Jul 28, 2026 at 10:35:34AM +0100, Bryan O'Donoghue wrote:
>> Add support for PHY API devices
> One thing I ran into while bringing this up on a Lenovo Yoga Slim 7x
> Gen 11 (Glymur, ov08x40 on CSIPHY4, two lanes), with Nihal's Glymur
> CAMSS series on top: the two ends of the CAMSS <-> PHY link count lanes
> differently, and the CAMSS side silently ends up on the wrong lanes.
>
> The csi2-phy binding numbers data-lanes from 1, and the PHY driver
> converts:
>
> /* Convert data-lanes = <1 2 3 4> to bit positions */
> csi2phy->stream_cfg.lane_cfg.data[i].pos = data_lanes[i] - 1;
>
> The CAMSS endpoint still takes its data-lanes as 0-based positions;
Resolved here:
https://lore.kernel.org/r/20260906-b4-linux-next-25-03-13-dtsi-x1e80100-camss-v17-5-e2197a3e2551@linaro.org
---
bod
next prev parent reply other threads:[~2026-09-16 14:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 9:35 [PATCH v13 0/5] Add dt-bindings and PHY updates for CAMSS on x1e80100 silicon Bryan O'Donoghue
2026-07-28 9:35 ` [PATCH v13 1/5] phy: core: Add phy_get_by_of_node() Bryan O'Donoghue
2026-07-28 9:35 ` [PATCH v13 2/5] phy: core: Add devm_phy_get_by_of_node() Bryan O'Donoghue
2026-07-28 10:46 ` Dmitry Baryshkov
2026-07-28 10:51 ` Bryan O'Donoghue
2026-07-28 9:35 ` [PATCH v13 3/5] media: qcom: camss: Add support for PHY API devices Bryan O'Donoghue
2026-07-28 10:48 ` Dmitry Baryshkov
2026-07-28 11:02 ` Loic Poulain
2026-07-29 13:45 ` Nihal Kumar Gupta
2026-07-29 20:31 ` Bryan O'Donoghue
2026-07-30 5:34 ` Nihal Kumar Gupta
2026-09-16 13:29 ` Oleg Keri
2026-09-16 14:43 ` Bryan O'Donoghue [this message]
2026-07-28 9:35 ` [PATCH v13 4/5] dt-bindings: media: qcom,x1e80100-camss: Describe iommu entries Bryan O'Donoghue
2026-07-28 14:44 ` Rob Herring
2026-07-29 9:05 ` Bryan O'Donoghue
2026-07-28 9:35 ` [PATCH v13 5/5] dt-bindings: media: qcom,x1e80100-camss: Make vdd-csiphy supplies optional Bryan O'Donoghue
2026-07-29 6:25 ` Krzysztof Kozlowski
2026-07-29 9:06 ` 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=b9693892-d0d3-49aa-8fb8-21da12f6eadc@kernel.org \
--to=bod@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=konradybcio@kernel.org \
--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=mchehab@kernel.org \
--cc=nihal.gupta@oss.qualcomm.com \
--cc=okerixx@gmail.com \
--cc=rfoss@kernel.org \
--cc=todor.too@gmail.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
all inboxes | Powered by JetHome®