From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Yunfei Dong <yunfei.dong@mediatek.com>,
Chen-Yu Tsai <wenst@chromium.org>,
Nicolas Dufresne <nicolas@ndufresne.ca>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Tiffany Lin <tiffany.lin@mediatek.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Fritz Koenig <frkoenig@chromium.org>,
Daniel Vetter <daniel@ffwll.ch>,
Steve Cho <stevecho@chromium.org>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH 1/5] media: mediatek: vcodec: add params to record lat and core lat_buf count
Date: Tue, 13 Dec 2022 10:09:54 +0100 [thread overview]
Message-ID: <7e668b90-e3e6-5d25-e894-f754662405af@collabora.com> (raw)
In-Reply-To: <20221210073218.17350-2-yunfei.dong@mediatek.com>
Il 10/12/22 08:32, Yunfei Dong ha scritto:
> Using lat_buf to share decoder information between lat and core work
> queue, adding params to record the buf count.
>
> Fixes: 365e4ba01df4 ("media: mtk-vcodec: Add work queue for core hardware decode")
> Signed-off-by: Yunfei Dong <yunfei.dong@mediatek.com>
> ---
> .../platform/mediatek/vcodec/vdec_msg_queue.c | 32 ++++++++++++++++++-
> .../platform/mediatek/vcodec/vdec_msg_queue.h | 9 ++++++
> 2 files changed, 40 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/mediatek/vcodec/vdec_msg_queue.c b/drivers/media/platform/mediatek/vcodec/vdec_msg_queue.c
> index dc2004790a47..af7ddba1923a 100644
> --- a/drivers/media/platform/mediatek/vcodec/vdec_msg_queue.c
> +++ b/drivers/media/platform/mediatek/vcodec/vdec_msg_queue.c
> @@ -52,6 +52,30 @@ static struct list_head *vdec_get_buf_list(int hardware_index, struct vdec_lat_b
> }
> }
>
> +static void vdec_msg_queue_inc(struct vdec_msg_queue *msg_queue, int hardware_index)
> +{
> + mutex_lock(&msg_queue->list_cnt_mutex);
I doubt that you need to use this mutex, as you're using atomics...
> +
> + if (hardware_index == MTK_VDEC_CORE)
> + atomic_inc(&msg_queue->core_list_cnt);
> + else
> + atomic_inc(&msg_queue->lat_list_cnt);
> +
This branch (with the relevant appropriate changes) can be simplified as
atomic_inc(&msg_queue->list_cnt[hardware_index]);
...where list_cnt is an array, and hardware_index is an enumeration.
> + mutex_unlock(&msg_queue->list_cnt_mutex);
> +}
> +
> +static void vdec_msg_queue_dec(struct vdec_msg_queue *msg_queue, int hardware_index)
> +{
> + mutex_lock(&msg_queue->list_cnt_mutex);
> +
> + if (hardware_index == MTK_VDEC_CORE)
> + atomic_dec(&msg_queue->core_list_cnt);
> + else
> + atomic_dec(&msg_queue->lat_list_cnt);
Same here.
> +
> + mutex_unlock(&msg_queue->list_cnt_mutex);
> +}
> +
Regards,
Angelo
next prev parent reply other threads:[~2022-12-13 9:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 7:32 [PATCH 0/5] media: mediatek: vcodec: Fix power_VideoCall test fail Yunfei Dong
2022-12-10 7:32 ` [PATCH 1/5] media: mediatek: vcodec: add params to record lat and core lat_buf count Yunfei Dong
2022-12-13 9:09 ` AngeloGioacchino Del Regno [this message]
2022-12-19 6:42 ` Yunfei Dong (董云飞)
2022-12-10 7:32 ` [PATCH 2/5] media: mediatek: vcodec: using each instance lat_buf count replace core ready list Yunfei Dong
2022-12-10 7:32 ` [PATCH 3/5] media: mediatek: vcodec: move lat_buf to the top of core list Yunfei Dong
2022-12-13 9:23 ` AngeloGioacchino Del Regno
2022-12-10 7:32 ` [PATCH 4/5] media: mediatek: vcodec: add core decode done event Yunfei Dong
2022-12-10 7:32 ` [PATCH 5/5] media: mediatek: vcodec: remove unused lat_buf Yunfei Dong
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=7e668b90-e3e6-5d25-e894-f754662405af@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.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=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=stevecho@chromium.org \
--cc=tiffany.lin@mediatek.com \
--cc=wenst@chromium.org \
--cc=yunfei.dong@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®