[PATCH 2/2] phy: qcom-mipi-csi2: Add a CSI2 MIPI D-PHY driver
Bryan O'Donoghue
bryan.odonoghue at linaro.org
Mon Jul 14 17:13:01 PDT 2025
On 14/07/2025 16:30, Vladimir Zapolskiy wrote:
>>
>> I think that is genuinely something we should handle in camss-csid.c
>> maybe with some meta-data inside of the ports/endpoints..
>>
>
> This is a CSIPHY property, a CSIPHY hardware configuration and a wiring
> of sensors to a CSIPHY. Where is the relation to CSID here? There is no.
All the PHY really needs to know is the # of lanes in aggregate, which
physical lanes to map to which logical lanes and the pixel clock.
We should add additional support to the Kernel's D-PHY API parameters
mechanism to support that physical-to-logical mapping but, that's not
required for this series or for any currently know upstream user of CAMSS.
> Please share at least a device tree node description, which supports
> a connection of two sensors to a single CSIPHY, like it shall be done
> expectedly.
&camss {
port at 0 {
csiphy0_lanes01_ep: endpoint0 {
data-lanes = <0 1>;
remote-endpoint = <&sensor0_ep>;
};
csiphy0_lanes23_ep: endpoint0 {
data-lanes = <2 3>;
remote-endpoint = <&sensor1_ep>;
};
};
};
&csiphy0 {
status = "okay";
vdda-0p8-supply = <&vreg_0p8>;
vdda-1p2-supply = <&vreg_1p2>;
phy-mode = <PHY_TYPE_DPHY>;
};
sensor0 {
compatible = "manufacturer,sensor0";
port {
sensor0_ep: endpoint {
data-lanes = <0 1>;
remote-endpoint = <&csiphy0_lanes01_ep>;
};
};
};
sensor1 {
compatible = "manufacturer,sensor1";
port {
sensor1_ep: endpoint {
data-lanes = <0 1>;
remote-endpoint = <&csiphy1_lanes23_ep>;
};
};
};
---
bod
More information about the linux-phy
mailing list