[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7fb34b98-7bc0-43fb-a6e7-dee073fed317@quicinc.com>
Date: Wed, 4 Sep 2024 22:20:36 +0800
From: Depeng Shao <quic_depengs@...cinc.com>
To: Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>, <rfoss@...nel.org>,
<todor.too@...il.com>, <bryan.odonoghue@...aro.org>,
<mchehab@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
<conor+dt@...nel.org>
CC: <linux-arm-msm@...r.kernel.org>, <linux-media@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<kernel@...cinc.com>
Subject: Re: [PATCH 04/13] media: qcom: camss: csiphy: Add an init callback to
CSI PHY devices
Hi Bryan,
On 8/19/2024 8:17 AM, Vladimir Zapolskiy wrote:
> On 8/12/24 17:41, Depeng Shao wrote:
>> From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
> I've already expressed concerns about a necessity of this function,
> since it
> adds runtime burden of work, which can be successfully done at compile
> time,
> but okay...
>
> Since it is needed for 3PH case only, it may make sense to remove it
> from 2PH
> and call it here conditionally like
>
> if (csiphy->res->hw_ops->init)
> ret = csiphy->res->hw_ops->init(csiphy);
>
> But it's up to you, I hope the callback will be removed in short future.
>
Could you please comment on if it is fine to remove the init from 2PH
driver?
Thanks,
Depeng
Powered by blists - more mailing lists