[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c9570c8e-c9a5-43f5-8b69-d5c38d214061@linaro.org>
Date: Fri, 8 Sep 2023 11:21:43 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Konrad Dybcio <konrad.dybcio@...aro.org>, rfoss@...nel.org,
todor.too@...il.com, agross@...nel.org, andersson@...nel.org,
mchehab@...nel.org, hverkuil-cisco@...all.nl,
laurent.pinchart@...asonboard.com, sakari.ailus@...ux.intel.com,
andrey.konovalov@...aro.org
Cc: linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 15/17] media: qcom: camss: Move vfe_disable into a
common routine where applicable
On 08/09/2023 11:04, Konrad Dybcio wrote:
> On 8.09.2023 12:02, Konrad Dybcio wrote:
>> On 7.09.2023 18:44, Bryan O'Donoghue wrote:
>>> We can move vfe_disable() into a common routine in the core VFE file
>>> provided we make wm_stop() a VFE specific callback.
>>>
>>> The callback is required to capture the case where VFE 17x currently isn't
>>> VC enabled where as VFE 480 is.
>>>
>>> Suggested-by: Laurent Pinchart <laurent.pinchart@...asonboard.com>
>>> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
>>> ---
>> Acked-by: Konrad Dybcio <konrad.dybcio@...aro.org>
>>
>> Konrad
> Actually there's
>
> ret = vfe_reset(vfe);
>
> return ret;
>
>
> which could just be
>
> return vfe_reset(vfe);
>
>
> Konrad
On purpose.
I prefer the ret = ; return ret; pattern since it makes it easier / less
work to
ret = fn();
if (ret)
goto error;
error:
return ret;
---
bod
Powered by blists - more mailing lists