From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
rfoss@kernel.org, todor.too@gmail.com, agross@kernel.org,
andersson@kernel.org, mchehab@kernel.org,
laurent.pinchart@ideasonboard.com, sakari.ailus@linux.intel.com,
andrey.konovalov@linaro.org
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 15/17] media: qcom: camss: Move vfe_disable into a common routine where applicable
Date: Mon, 11 Sep 2023 11:10:47 +0200 [thread overview]
Message-ID: <be6b41e0-c610-49c3-ae6c-e811b56aca30@xs4all.nl> (raw)
In-Reply-To: <e1ab1df4-8431-483d-8f20-74de5349cfbc@linaro.org>
On 08/09/2023 12:36, Bryan O'Donoghue wrote:
> On 08/09/2023 11:24, Konrad Dybcio wrote:
>> On 8.09.2023 12:21, Bryan O'Donoghue wrote:
>>> 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@ideasonboard.com>
>>>>>> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
>>>>>> ---
>>>>> Acked-by: Konrad Dybcio <konrad.dybcio@linaro.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;
>> There's no error label in vfe_disable_output
>>
>> Konrad
>
> No there is not. Its a pattern I use to make adding jump labels easier later on.
This adds a bunch of extra lines just in case something might happen in the
future. That is generally a bad idea, so please change this. As you can see
it just causes reviewers to trip over this with exactly the question you got
here.
>
> Just like you use the pattern of appending "," to aggregate initialisation.
Adding a comma at the end doesn't add extra lines. To be honest, I don't
have a strong opinion on this either way. Personally I would probably use a
comma if it is likely that the list would be extended in the future, and
leave it out if I am pretty certain that won't happen. In any case, I don't
mind either way.
Regards,
Hans
>
> ---
> bod
next prev parent reply other threads:[~2023-09-11 21:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 16:43 [PATCH v4 00/17] media: qcom: camss: Add parameter passing to remove several outstanding bugs Bryan O'Donoghue
2023-09-07 16:43 ` [PATCH v4 01/17] media: qcom: camss: Amalgamate struct resource with struct resource_ispif Bryan O'Donoghue
2023-09-07 16:43 ` [PATCH v4 02/17] media: qcom: camss: Rename camss struct resources to camss_subdev_resources Bryan O'Donoghue
2023-09-08 9:13 ` Konrad Dybcio
2023-09-07 16:43 ` [PATCH v4 03/17] media: qcom: camss: Start to move to module compat matched resources Bryan O'Donoghue
2023-09-07 16:43 ` [PATCH v4 04/17] media: qcom: camss: Pass icc bandwidth table as a platform parameter Bryan O'Donoghue
2023-09-07 16:43 ` [PATCH v4 05/17] media: qcom: camss: Pass remainder of variables as resources Bryan O'Donoghue
2023-09-07 16:43 ` [PATCH v4 06/17] media: qcom: camss: Pass line_num from compat resources Bryan O'Donoghue
2023-09-07 16:44 ` [PATCH v4 07/17] media: qcom: camss: Pass CAMSS subdev callbacks via resource ops pointer Bryan O'Donoghue
2023-09-08 9:14 ` Konrad Dybcio
2023-09-07 16:44 ` [PATCH v4 08/17] media: qcom: camss: Assign the correct number of RDIs per VFE Bryan O'Donoghue
2023-09-07 16:44 ` [PATCH v4 09/17] media: qcom: camss: Remove special case for VFE get/put Bryan O'Donoghue
2023-09-07 16:44 ` [PATCH v4 10/17] media: qcom: camss: Untangle if/else spaghetti in camss Bryan O'Donoghue
2023-09-07 16:44 ` [PATCH v4 11/17] media: qcom: camss: Allow clocks vfeN vfe_liteN or vfe_lite Bryan O'Donoghue
2023-09-08 9:19 ` Konrad Dybcio
2023-09-07 16:44 ` [PATCH v4 12/17] media: qcom: camss: Functionally decompose CSIPHY clock lookups Bryan O'Donoghue
2023-09-08 9:20 ` Konrad Dybcio
2023-09-08 9:21 ` Konrad Dybcio
2023-09-07 16:44 ` [PATCH v4 13/17] media: qcom: camss: Fix support for setting CSIPHY clock name csiphyX Bryan O'Donoghue
2023-09-07 16:44 ` [PATCH v4 14/17] media: qcom: camss: Support RDI3 for VFE 17x Bryan O'Donoghue
2023-09-07 16:44 ` [PATCH v4 15/17] media: qcom: camss: Move vfe_disable into a common routine where applicable Bryan O'Donoghue
2023-09-08 10:02 ` Konrad Dybcio
2023-09-08 10:04 ` Konrad Dybcio
2023-09-08 10:21 ` Bryan O'Donoghue
2023-09-08 10:24 ` Konrad Dybcio
2023-09-08 10:36 ` Bryan O'Donoghue
2023-09-11 9:10 ` Hans Verkuil [this message]
2023-09-07 16:44 ` [PATCH v4 16/17] media: qcom: camss: Propagate vfe_reset error up the callstack Bryan O'Donoghue
2023-09-08 10:03 ` Konrad Dybcio
2023-09-07 16:44 ` [PATCH v4 17/17] media: qcom: camss: Comment CSID dt_id field Bryan O'Donoghue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be6b41e0-c610-49c3-ae6c-e811b56aca30@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andrey.konovalov@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=todor.too@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®