[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6f9b7047-7471-4fdf-89ae-d78c1c92690a@linaro.org>
Date: Wed, 4 Sep 2024 15:51:52 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Depeng Shao <quic_depengs@...cinc.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>, rfoss@...nel.org,
todor.too@...il.com, 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
On 04/09/2024 15:20, Depeng Shao wrote:
> 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
Yes, its dead code ATM we can enumerate this callback when/if its needed.
Agreed.
---
bod
Powered by blists - more mailing lists