Re: [PATCH v13 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema

[Bryan O'Donoghue]

On 21/07/2026 14:35, Vladimir Zapolskiy wrote:
> > Had a brief discussion with Vlad, Neil and Vinod
> >
> > Resolution:
> >
> > - phys = <> retained
>
> It should suffice as an optional property, moreover any kind of
> phy interface usage is not supposed to be done from CSID driver.
>
> > - phy-cells = <0>
> > - bus-type from the media-controller
> >     Already specified with camss still aligns with Rob's declaration
> >     "the consumer defines the mode" so I'm comfortable with this
> >     compromise position.
> >     This will still facilitate CPHY work/mode-selection via
> >     phy_ops->configure() with how to define the CPHY part TBD.
>
> As it was discussed there should be no phy specific interfaces
> between this phy driver and CAMSS driver.

I'm probably not getting this point, sorry about that. For clarity 
though CAMSS will use phys = <> and the PHY API phy_get(), 
phy_power_on(), or phy_configure() as there's no other possible 
interface to this driver.

> > - data-lanes = <0 1 2 3> valid
>
> Would be nice to get an ack from linux-media maintainers on it.
> > - MAX_LANES 8 instead of MAX_DATA_LANES 7
>
> Since 'data-lanes' value follows some register bits and not
> the actual PCB lanes as in video-intefaces.yaml, this shall be
> explicitly described in the CSIPHY dt binding documentation.

Yes we said that.
> > - v14 with these changes shortly.

---
bod