From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Stephen Boyd <swboyd@chromium.org>,
Abhinav Kumar <abhinavk@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>
Cc: David Airlie <airlied@linux.ie>,
linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4 5/5] drm/msm/dpu: move VBIF blocks handling to dpu_rm
Date: Sat, 22 Jan 2022 00:01:02 +0300 [thread overview]
Message-ID: <a6e5fb27-8a0f-44bf-c4d3-0619d8fc834f@linaro.org> (raw)
In-Reply-To: <CAE-0n505KAiLvza2WTRfk8w9qcAH-Z2W6kLMtrOxTNRbUnSJig@mail.gmail.com>
On 07/01/2022 04:27, Stephen Boyd wrote:
> Quoting Dmitry Baryshkov (2022-01-05 15:10:31)
>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c
>> index bf4d72356a12..2301ac114920 100644
>> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c
>> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c
>> @@ -78,6 +78,10 @@ int dpu_rm_destroy(struct dpu_rm *rm)
>> if (rm->hw_intf[i])
>> dpu_hw_intf_destroy(rm->hw_intf[i]);
>> }
>> + for (i = 0; i < ARRAY_SIZE(rm->hw_vbif); i++) {
>> + if (rm->hw_vbif[i])
>> + dpu_hw_vbif_destroy(rm->hw_vbif[i]);
>
> Maybe drop this check and pass NULL to dpu_hw_vbif_destroy() sometimes?
> Then the check can be omitted and the braces dropped
Nice idea. This also applies to dpu_hw_intf_destroy, so I'm going to
apply it to the previous patch.
>
>> + }
>>
>> return 0;
>> }
>> @@ -212,6 +216,23 @@ int dpu_rm_init(struct dpu_rm *rm,
>> rm->dspp_blks[dspp->id - DSPP_0] = &hw->base;
>> }
>>
>> + for (i = 0; i < cat->vbif_count; i++) {
>> + struct dpu_hw_vbif *hw;
>> + const struct dpu_vbif_cfg *vbif = &cat->vbif[i];
>> +
>> + if (vbif->id < VBIF_0 || vbif->id >= VBIF_MAX) {
>> + DPU_ERROR("skip vbif %d with invalid id\n", vbif->id);
>> + continue;
>> + }
>> + hw = dpu_hw_vbif_init(vbif->id, mmio, cat);
>> + if (IS_ERR_OR_NULL(hw)) {
>> + rc = PTR_ERR(hw);
>> + DPU_ERROR("failed vbif object creation: err %d\n", rc);
>> + goto fail;
>
> If it's NULL then rc will be 0 and fail will return 0. Is that
> intentional?
Actually no. And init functions can not return NULL. So let's fix it too.
>
>> + }
>> + rm->hw_vbif[vbif->id - VBIF_0] = hw;
>> + }
>> +
>> return 0;
>>
>> fail:
--
With best wishes
Dmitry
prev parent reply other threads:[~2022-01-21 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 23:10 [PATCH v4 0/5] drm/msm/dpu: simplify RM code Dmitry Baryshkov
2022-01-05 23:10 ` [PATCH v4 1/5] drm/msm/dpu: drop unused lm_max_width from RM Dmitry Baryshkov
2022-01-07 0:53 ` Stephen Boyd
2022-01-05 23:10 ` [PATCH v4 2/5] drm/msm/dpu: add DSPP blocks teardown Dmitry Baryshkov
2022-01-07 0:54 ` Stephen Boyd
2022-01-05 23:10 ` [PATCH v4 3/5] drm/msm/dpu: get INTF blocks directly rather than through RM Dmitry Baryshkov
2022-01-07 1:01 ` Stephen Boyd
2022-01-05 23:10 ` [PATCH v4 4/5] drm/msm/dpu: stop embedding dpu_hw_blk into dpu_hw_intf Dmitry Baryshkov
2022-01-07 1:20 ` Stephen Boyd
2022-01-07 1:21 ` Stephen Boyd
2022-01-05 23:10 ` [PATCH v4 5/5] drm/msm/dpu: move VBIF blocks handling to dpu_rm Dmitry Baryshkov
2022-01-07 1:27 ` Stephen Boyd
2022-01-21 21:01 ` Dmitry Baryshkov [this message]
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=a6e5fb27-8a0f-44bf-c4d3-0619d8fc834f@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).