From: "Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>
To: "chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"eugen.hristev@collabora.com" <eugen.hristev@collabora.com>
Cc: "linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Singo Chang (張興國)" <Singo.Chang@mediatek.com>,
"Johnson Wang (王聖鑫)" <Johnson.Wang@mediatek.com>,
"Jason-ch Chen (陳建豪)" <Jason-ch.Chen@mediatek.com>,
"Shawn Sung (宋孝謙)" <Shawn.Sung@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Subject: Re: [PATCH v7 2/4] drm/mediatek: Fix using wrong drm private data to bind mediatek-drm
Date: Mon, 31 Jul 2023 08:21:28 +0000 [thread overview]
Message-ID: <6c07d1bc12c9226bf623da0a46ffaadb151c2175.camel@mediatek.com> (raw)
In-Reply-To: <d74f959b-2255-4587-e99c-2c6b043dc44c@collabora.com>
Hi Eugen,
Thanks for the reviews.
On Fri, 2023-07-28 at 11:47 +0300, Eugen Hristev wrote:
> Hi,
>
> On 7/27/23 19:41, Jason-JH.Lin wrote:
> > Add checking the length of each data path before assigning 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>
> > ---
> > 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 249c9fd6347e..d2fb1fb4e682 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) {
> > + if (temp_drm_priv->mtk_drm_bound)
> > + cnt++;
> > +
> > + if (temp_drm_priv->data->main_len)
> > + all_drm_priv[0] = temp_drm_priv;
> > + else if (temp_drm_priv->data->ext_len)
> > + all_drm_priv[1] = temp_drm_priv;
> > + else if (temp_drm_priv->data->third_len)
> > + all_drm_priv[2] = temp_drm_priv;
> > + }
>
> Previously the code was assigning stuff into all_drm_priv[cnt] and
> incrementing it.
> With your change, it assigns to all_drm_priv[0], [1], [2]. Is this
> what
> you intended ?
Because dev_get_drvdata(drm_dev) will get the driver data by drm_dev.
Each drm_dev represents a display path.
e,g.
drm_dev of "mediatek,mt8195-vdosys0" represents main path.
drm_dev of "mediatek,mt8195-vdosys1" represents ext path.
So we want to make sure all_drm_priv[] store the private data in
the order of display path, such as:
all_drm_priv[0] = the private data of main display
all_drm_priv[1] = the private data of ext display
all_drm_priv[2] = the private data of third display
> If this loop has second run, you will reassign to all_drm_priv again
> ?
Because the previous code will store all_drm_priv[] in the order of
mtk_drm_bind() was called.
If drm_dev of ext path bound earlier than drm_dev of main path,
all_drm_priv[] in mtk_drm_get_all_drm_priv() may be re-assigned like
this:
all_drm_priv[0]->all_drm_priv[0] = private data of ext path
all_drm_priv[1]->all_drm_priv[0] = private data of ext path
all_drm_priv[0]->all_drm_priv[1] = private data of main path
all_drm_priv[1]->all_drm_priv[1] = private data of main path
But we expect all_drm_priv[] be re-assigned like this:
all_drm_priv[0]->all_drm_priv[0] = private data of main path
all_drm_priv[1]->all_drm_priv[0] = private data of main path
all_drm_priv[0]->all_drm_priv[1] = private data of ext path
all_drm_priv[1]->all_drm_priv[1] = private data of ext path
> I would expect you to take `cnt` into account.
> Also, is it expected that all_drm_priv has holes in the array ?
Each drm_dev will only called mtk_drm_bind() once, so all holes
will be filled after all drm_dev has called mtk_drm_bind().
Do you agree with this statement? :)
Regards,
Jason-JH.Lin
>
> Eugen
>
>
>
> > }
> >
> > if (drm_priv->data->mmsys_dev_num == cnt) {
>
>
next prev parent reply other threads:[~2023-07-31 8:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230727164114.20638-1-jason-jh.lin@mediatek.com>
[not found] ` <20230727164114.20638-2-jason-jh.lin@mediatek.com>
2023-07-28 7:53 ` [PATCH v7 1/4] drm/mediatek: Add mmsys_dev_num to mt8188 vdosys0 driver data CK Hu (胡俊光)
2023-07-28 8:11 ` AngeloGioacchino Del Regno
[not found] ` <20230727164114.20638-4-jason-jh.lin@mediatek.com>
2023-07-28 8:11 ` [PATCH v7 3/4] drm/mediatek: Add ability to support dynamic connector selection AngeloGioacchino Del Regno
2023-07-31 9:37 ` Jason-JH Lin (林睿祥)
2023-07-28 9:56 ` CK Hu (胡俊光)
2023-07-31 10:08 ` Jason-JH Lin (林睿祥)
2023-07-31 10:27 ` CK Hu (胡俊光)
2023-07-31 6:37 ` CK Hu (胡俊光)
2023-08-02 5:59 ` Jason-JH Lin (林睿祥)
[not found] ` <20230727164114.20638-5-jason-jh.lin@mediatek.com>
2023-07-28 8:14 ` [PATCH v7 4/4] drm/mediatek: Add DSI support for mt8188 vdosys0 AngeloGioacchino Del Regno
2023-07-31 16:08 ` Jason-JH Lin (林睿祥)
[not found] ` <20230727164114.20638-3-jason-jh.lin@mediatek.com>
2023-07-28 8:03 ` [PATCH v7 2/4] drm/mediatek: Fix using wrong drm private data to bind mediatek-drm CK Hu (胡俊光)
2023-07-28 8:11 ` AngeloGioacchino Del Regno
2023-07-28 8:47 ` Eugen Hristev
2023-07-31 8:21 ` Jason-JH Lin (林睿祥) [this message]
2023-07-31 8:32 ` Eugen Hristev
2023-08-02 7:05 ` 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=6c07d1bc12c9226bf623da0a46ffaadb151c2175.camel@mediatek.com \
--to=jason-jh.lin@mediatek.com \
--cc=Jason-ch.Chen@mediatek.com \
--cc=Johnson.Wang@mediatek.com \
--cc=Nancy.Lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Shawn.Sung@mediatek.com \
--cc=Singo.Chang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eugen.hristev@collabora.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 \
/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
Powered by JetHome