From: "Ming Qian(OSS)" <ming.qian@oss.nxp.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-media@vger.kernel.org, mchehab@kernel.org,
hverkuil-cisco@xs4all.nl, nicolas@ndufresne.ca,
benjamin.gaignard@collabora.com, p.zabel@pengutronix.de,
sebastian.fricke@collabora.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com, l.stach@pengutronix.de,
Frank.li@nxp.com, peng.fan@nxp.com, eagle.zhou@nxp.com,
imx@lists.linux.dev, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/3] Fix concurrency issues between G1 and G2 on
Date: Wed, 31 Dec 2025 13:37:22 +0800 [thread overview]
Message-ID: <3397e2c8-602f-4cd8-8cd5-7af3410edc00@oss.nxp.com> (raw)
In-Reply-To: <CAPDyKFpFm9kCSNbALJTqeyzFdg3OoooE2gUOXJcjv=WgQeZ84Q@mail.gmail.com>
Hi Uffe,
On 12/30/2025 9:42 PM, Ulf Hansson wrote:
> On Fri, 5 Dec 2025 at 02:55, <ming.qian@oss.nxp.com> wrote:
>>
>> From: Ming Qian <ming.qian@oss.nxp.com>
>>
>> On the i.MX8MQ, we encountered some concurrency issues with H264 and HEVC
>> decoding.
>>
>> There are two main reasons:
>> 1. The vpu blk-ctrl don't have separate reset and clock enable bits.
>> 2. The g1 VPU and g2 VPU cannot decode simultaneously.
>>
>> We attempted to make corresponding fix to address these two issues.
>>
>> Ming Qian (2):
>> pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu
>> media: verisilicon: Avoid G2 bus error while decoding H.264 and HEVC
>>
>> Nicolas Dufresne (1):
>> media: v4l2-mem2mem: Add a kref to the v4l2_m2m_dev structure
>>
>> drivers/media/platform/verisilicon/hantro.h | 2 +
>> .../media/platform/verisilicon/hantro_drv.c | 42 +++++++++++++++++--
>> .../media/platform/verisilicon/imx8m_vpu_hw.c | 8 ++++
>> drivers/media/v4l2-core/v4l2-mem2mem.c | 23 ++++++++++
>> drivers/pmdomain/imx/imx8m-blk-ctrl.c | 11 +++--
>> include/media/v4l2-mem2mem.h | 21 ++++++++++
>> 6 files changed, 100 insertions(+), 7 deletions(-)
>>
>
> Can I pick the pmdomain patch separately from the others? Or does this
> need to go together?
>
> Kind regards
> Uffe
I think you can pick the pmdomain patch separately.
Regards,
Ming
next prev parent reply other threads:[~2025-12-31 5:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 1:54 [PATCH v4 0/3] Fix concurrency issues between G1 and G2 on ming.qian
2025-12-05 1:54 ` [PATCH v4 1/3] media: v4l2-mem2mem: Add a kref to the v4l2_m2m_dev structure ming.qian
2025-12-05 15:08 ` Frank Li
2025-12-30 13:39 ` Ulf Hansson
2026-01-05 18:08 ` Nicolas Dufresne
2026-01-06 13:28 ` Ulf Hansson
2025-12-05 1:54 ` [PATCH v4 2/3] pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu ming.qian
2026-01-03 10:02 ` Ulf Hansson
2025-12-05 1:54 ` [PATCH v4 3/3] media: verisilicon: Avoid G2 bus error while decoding H.264 and HEVC ming.qian
2025-12-05 15:09 ` Frank Li
2025-12-30 13:42 ` [PATCH v4 0/3] Fix concurrency issues between G1 and G2 on Ulf Hansson
2025-12-31 5:37 ` Ming Qian(OSS) [this message]
2026-01-05 18:10 ` Nicolas Dufresne
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=3397e2c8-602f-4cd8-8cd5-7af3410edc00@oss.nxp.com \
--to=ming.qian@oss.nxp.com \
--cc=Frank.li@nxp.com \
--cc=benjamin.gaignard@collabora.com \
--cc=eagle.zhou@nxp.com \
--cc=festevam@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.fricke@collabora.com \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.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