[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b1dc3644-8df0-4147-94ae-1cfed835b9a0@linaro.org>
Date: Thu, 13 Nov 2025 09:27:57 +0000
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: David Heidelberg <david@...t.cz>, Robert Foss <rfoss@...nel.org>,
Todor Tomov <todor.too@...il.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Luca Weiss <luca.weiss@...rphone.com>, Petr Hodina <phodina@...tonmail.com>,
Casey Connolly <casey.connolly@...aro.org>, "Dr. Git" <drgitx@...il.com>
Cc: Joel Selvaraj <foss@...lselvaraj.com>, linux-media@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
phone-devel@...r.kernel.org
Subject: Re: [PATCH RFC 2/8] media: qcom: camss: csiphy: Introduce C-PHY
On 12/11/2025 16:15, David Heidelberg wrote:
>> Should be an integer from
>>
>> include/dt-bindings/phy/phy.h
>>
>> - PHY_TYPE_DPHY
>> - PHY_TYPE_CPHY
>>
>> this should be indicated in the dt and latched here.
>
> Would it make sense to rather use the int from:
>
> include/dt-bindings/media/video-interfaces.h
>
> - MEDIA_BUS_TYPE_CSI2_CPHY
> - MEDIA_BUS_TYPE_CSI2_DPHY
> - ...
>
> ?
Maybe, but surely you need to get the mode of the PHY from DT ?
I'm fine with the MEDIA_BUS_TYPE but, I do think the logic must be DT
driven.
---
bod
Powered by blists - more mailing lists