From: "Yunfei Dong (董云飞)" <Yunfei.Dong@mediatek.com>
To: "sebastian.fricke@collabora.com" <sebastian.fricke@collabora.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"frkoenig@chromium.org" <frkoenig@chromium.org>,
"stevecho@chromium.org" <stevecho@chromium.org>,
"nhebert@chromium.org" <nhebert@chromium.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"benjamin.gaignard@collabora.com"
<benjamin.gaignard@collabora.com>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"hsinyi@chromium.org" <hsinyi@chromium.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"nfraprado@collabora.com" <nfraprado@collabora.com>
Subject: Re: [PATCH] media: mediatek: vcodec: support 36bit physical address
Date: Wed, 6 Mar 2024 08:07:58 +0000 [thread overview]
Message-ID: <a8c9ec95ace5b6749d28b7e81151b371700bcc03.camel@mediatek.com> (raw)
In-Reply-To: <20240301095217.bmsnizobpb736fgg@basti-XPS-13-9310>
Hi Sebastian,
Thanks for your advice.
On Fri, 2024-03-01 at 10:52 +0100, Sebastian Fricke wrote:
> Hey Yunfei,
>
> On 01.03.2024 10:01, Yunfei Dong wrote:
> > The physical address is beyond 32bit for mt8188 platform, need
> > to change the type from unsigned int to unsigned long in case of
> > the high bit missing.
>
> I would reword this a bit, the address is not beyond 32 bit, which
> would
> could be interpret as if the address starts after 32nd bit, instead
> it
> is larger than 32bits. Secondly, we don't change the type in case the
> high bit is missing, we change the type unconditionally, we do change
> the type so that the high bit isn't missing.
>
> My suggestion:
>
> The physical address on the MT8188 platform is larger than 32 bits,
> change the type from unsigned int to unsigned long to be able to
> access
> the high bits of the address.
>
I will rewrite the commit message according to your advice.
> One more question below...
>
> >
> > Signed-off-by: Yunfei Dong <yunfei.dong@mediatek.com>
> > ---
> > .../mediatek/vcodec/decoder/vdec/vdec_vp9_req_lat_if.c | 4
> > ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git
> > a/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_vp9_req_
> > lat_if.c
> > b/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_vp9_req_
> > lat_if.c
> > index cf48d09b78d7..85df3e7c2983 100644
> > ---
> > a/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_vp9_req_
> > lat_if.c
> > +++
> > b/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_vp9_req_
> > lat_if.c
> > @@ -1074,7 +1074,7 @@ static int
> > vdec_vp9_slice_setup_tile_buffer(struct vdec_vp9_slice_instance
> > *inst
> > unsigned int mi_row;
> > unsigned int mi_col;
> > unsigned int offset;
> > - unsigned int pa;
> > + unsigned long pa;
> > unsigned int size;
> > struct vdec_vp9_slice_tiles *tiles;
> > unsigned char *pos;
> > @@ -1109,7 +1109,7 @@ static int
> > vdec_vp9_slice_setup_tile_buffer(struct vdec_vp9_slice_instance
> > *inst
> > pos = va + offset;
> > end = va + bs->size;
> > /* truncated */
> > - pa = (unsigned int)bs->dma_addr + offset;
> > + pa = (unsigned long)bs->dma_addr + offset;
>
> I can see in other parts of the driver that bs->dma_addr is converted
> to
> u64 or uint64_t. Is unsigned long always 64-bit on the different
> Mediatek platforms? If so, why do you prefer unsigned long over u64?
> (Which describes the type more precisely)
>
For 64-bit system, unsigned long is u64 or uint64_t.
The pa is over 32bit for mt8188(64bit system).
The pa is 32bit for mt8195/mt8192/mt8186 etc(64bit system).
pa = (unsigned long)bs->dma_addr + offset;
-> I need to remove 'unsigned long' before bs->dma_addr.
For 32bit pa, the high bit is zero, won't influence the hardware
decoder.
Best Regards,
Yunfei Dong
> (Same applies for:
> drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_vp8_if.c:452
> )
>
Ok, I will change it in next patch.
> Greetings,
> Sebastian
>
> > tb = instance->tile.va;
> > for (i = 0; i < rows; i++) {
> > for (j = 0; j < cols; j++) {
> > --
> > 2.18.0
> >
> >
prev parent reply other threads:[~2024-03-06 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 2:01 [PATCH] media: mediatek: vcodec: support 36bit physical address Yunfei Dong
2024-03-01 9:03 ` AngeloGioacchino Del Regno
2024-03-01 9:23 ` Yunfei Dong (董云飞)
2024-03-01 9:36 ` AngeloGioacchino Del Regno
2024-03-01 9:54 ` Sebastian Fricke
2024-03-01 9:52 ` Sebastian Fricke
2024-03-06 8:07 ` Yunfei Dong (董云飞) [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=a8c9ec95ace5b6749d28b7e81151b371700bcc03.camel@mediatek.com \
--to=yunfei.dong@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=benjamin.gaignard@collabora.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=frkoenig@chromium.org \
--cc=hsinyi@chromium.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=nfraprado@collabora.com \
--cc=nhebert@chromium.org \
--cc=nicolas.dufresne@collabora.com \
--cc=sebastian.fricke@collabora.com \
--cc=stevecho@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