From: Eugen Hristev <eugen.hristev@collabora.com>
To: "Jason-JH.Lin" <jason-jh.lin@mediatek.com>,
Chun-Kuang Hu <chunkuang.hu@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
Jason-ch Chen <jason-ch.chen@mediatek.com>,
Johnson Wang <johnson.wang@mediatek.com>,
Singo Chang <singo.chang@mediatek.com>,
Nancy Lin <nancy.lin@mediatek.com>,
Shawn Sung <shawn.sung@mediatek.com>,
dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v8 3/8] drm/mediatek: Fix using wrong drm private data to bind mediatek-drm
Date: Thu, 3 Aug 2023 16:22:45 +0300 [thread overview]
Message-ID: <3d5de892-8311-86e8-b962-0e564903b0e6@collabora.com> (raw)
In-Reply-To: <20230802144802.751-4-jason-jh.lin@mediatek.com>
On 8/2/23 17:47, Jason-JH.Lin wrote:
> In mtk_drm_kms_init(), each element in all_drm_priv should has one
> display path private data only, such as:
> all_drm_priv[CRTC_MAIN] should has main_path data only
> all_drm_priv[CRTC_EXT] should has ext_path data only
> all_drm_priv[CRTC_THIRD] should has third_path data only
s/should has/should have/ ?
>
> So we need to add the length checking for each display path before
> assigning their drm private data into all_drm_priv array.
>
> Fixes: 1ef7ed48356c ("drm/mediatek: Modify mediatek-drm for mt8195 multi mmsys support")
> Signed-off-by: Jason-JH.Lin <jason-jh.lin@mediatek.com>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Reviewed-by: CK Hu <ck.hu@mediatek.com>
> ---
> drivers/gpu/drm/mediatek/mtk_drm_drv.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/mediatek/mtk_drm_drv.c b/drivers/gpu/drm/mediatek/mtk_drm_drv.c
> index 89a38561ba27..c12886f31e54 100644
> --- a/drivers/gpu/drm/mediatek/mtk_drm_drv.c
> +++ b/drivers/gpu/drm/mediatek/mtk_drm_drv.c
> @@ -351,6 +351,7 @@ static bool mtk_drm_get_all_drm_priv(struct device *dev)
> {
> struct mtk_drm_private *drm_priv = dev_get_drvdata(dev);
> struct mtk_drm_private *all_drm_priv[MAX_CRTC];
> + struct mtk_drm_private *temp_drm_priv;
> struct device_node *phandle = dev->parent->of_node;
> const struct of_device_id *of_id;
> struct device_node *node;
> @@ -373,9 +374,18 @@ static bool mtk_drm_get_all_drm_priv(struct device *dev)
> if (!drm_dev || !dev_get_drvdata(drm_dev))
> continue;
>
> - all_drm_priv[cnt] = dev_get_drvdata(drm_dev);
> - if (all_drm_priv[cnt] && all_drm_priv[cnt]->mtk_drm_bound)
> - cnt++;
> + temp_drm_priv = dev_get_drvdata(drm_dev);
> + if (temp_drm_priv) {
This is inside a 'for' loop right ?
Why don't you just 'continue' if temp_drm_priv is null ?
> + if (temp_drm_priv->mtk_drm_bound)
> + cnt++;
> +
> + if (temp_drm_priv->data->main_len)
> + all_drm_priv[CRTC_MAIN] = temp_drm_priv;
> + else if (temp_drm_priv->data->ext_len)
> + all_drm_priv[CRTC_EXT] = temp_drm_priv;
> + else if (temp_drm_priv->data->third_len)
> + all_drm_priv[CRTC_THIRD] = temp_drm_priv;
> + }
> }
>
> if (drm_priv->data->mmsys_dev_num == cnt) {
next prev parent reply other threads:[~2023-08-03 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230802144802.751-1-jason-jh.lin@mediatek.com>
[not found] ` <20230802144802.751-3-jason-jh.lin@mediatek.com>
2023-08-03 13:18 ` [PATCH v8 2/8] drm/mediatevk: Add crtc path enum for all_drm_priv array Eugen Hristev
2023-08-05 7:27 ` Jason-JH Lin (林睿祥)
[not found] ` <20230802144802.751-4-jason-jh.lin@mediatek.com>
2023-08-03 13:22 ` Eugen Hristev [this message]
2023-08-05 8:05 ` [PATCH v8 3/8] drm/mediatek: Fix using wrong drm private data to bind mediatek-drm Jason-JH Lin (林睿祥)
[not found] ` <20230802144802.751-5-jason-jh.lin@mediatek.com>
2023-08-03 13:27 ` [PATCH v8 4/8] drm/mediatek: Add encoder_index function to mtk_ddp_comp_funcs Eugen Hristev
2023-08-05 7:40 ` Jason-JH Lin (林睿祥)
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=3d5de892-8311-86e8-b962-0e564903b0e6@collabora.com \
--to=eugen.hristev@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason-ch.chen@mediatek.com \
--cc=jason-jh.lin@mediatek.com \
--cc=johnson.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nancy.lin@mediatek.com \
--cc=shawn.sung@mediatek.com \
--cc=singo.chang@mediatek.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®