From: Brandon Brnich <b-brnich@ti.com>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>,
"jackson.lee" <jackson.lee@chipsnmedia.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
"bob.beckett@collabora.com" <bob.beckett@collabora.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lafley.kim" <lafley.kim@chipsnmedia.com>,
"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
Nas Chung <nas.chung@chipsnmedia.com>
Subject: Re: [PATCH v5 4/4] media: chips-media: wave5: Improve performance of decoder
Date: Wed, 24 Sep 2025 10:06:24 -0500 [thread overview]
Message-ID: <76e12732-9a39-409d-aa60-44622fe42ec5@ti.com> (raw)
In-Reply-To: <6eed102e2aa739e5026ee545a38ddacf09058bbb.camel@collabora.com>
Hi Nicolas and Jackson,
On 9/24/2025 8:20 AM, Nicolas Dufresne wrote:
> Hi Jackson,
>
> Le mercredi 24 septembre 2025 à 01:14 +0000, jackson.lee a écrit :
>> Hi Nicolas
>>
>>> -----Original Message-----
>>> From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
>>> Sent: Tuesday, September 23, 2025 3:00 AM
>>> To: Brandon Brnich <b-brnich@ti.com>; jackson.lee
>>> <jackson.lee@chipsnmedia.com>; mchehab@kernel.org; hverkuil-
>>> cisco@xs4all.nl; bob.beckett@collabora.com
>>> Cc: linux-media@vger.kernel.org; linux-kernel@vger.kernel.org; lafley.kim
>>> <lafley.kim@chipsnmedia.com>; hverkuil@xs4all.nl; Nas Chung
>>> <nas.chung@chipsnmedia.com>
>>> Subject: Re: [PATCH v5 4/4] media: chips-media: wave5: Improve performance
>>> of decoder
>>>
>>> Hi Brandon,
>>>
>>> Le lundi 22 septembre 2025 à 12:32 -0500, Brandon Brnich a écrit :
>>>>> - /*
>>>>> - * During a resolution change and while draining, the firmware
>>>>> may
>>>>> flush
>>>>> - * the reorder queue regardless of having a matching decoding
>>>>> operation
>>>>> - * pending. Only terminate the job if there are no more IRQ
>>>>> coming.
>>>>> - */
>>>>> - wave5_vpu_dec_give_command(inst, DEC_GET_QUEUE_STATUS,
>>>>> &q_status);
>>>>> - if (q_status.report_queue_count == 0 &&
>>>>> - (q_status.instance_queue_count == 0 ||
>>>>> dec_info.sequence_changed)) {
>>>>> - dev_dbg(inst->dev->dev, "%s: finishing job.\n",
>>>>> __func__);
>>>>> - pm_runtime_mark_last_busy(inst->dev->dev);
>>>>
>>>> Patch is failing to apply here to linux-next because these redundant
>>>> calls have already been removed[0].
>>>
>>> Which have not been merged back from the RC into media-committers/next,
>>> forcing to skip a cycle. Jackson, feel free to rebase on linux-next like
>>> Brandon suggest.
>>
>> Then should I make v6 patch series based on Linux-next ?
>
> I've asked advises from the other maintainers, and the answer is no. Basing it
> on our next branch for linux-media submission is the correct thing to do. Its
> too late for this cycle, but be reassured we will improve our process in future
> iterations to reduce the risk of this happening.
>
> Feel free to send a rebased patch to Brandon, having more testing is always
> good.
Sorry for the confusion here, I was unaware that the patches weren't
present in -next on linux-media tree. Typically I just do all my testing
on the linux-next branch. I will make sure to use linux-media in the future.
No need to share the patch with me, I already rebased it to build and
start my own testing.
Thanks,
Brandon
>
> cheers,
> Nicolas
>
>>
>> Thanks
>> Jackson
>>
>>>
>>> regards,
>>
>>> Nicolas
next prev parent reply other threads:[~2025-09-24 15:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 5:52 [PATCH v5 0/4] Performance improvement " Jackson.lee
2025-09-22 5:52 ` [PATCH v5 1/4] media: chips-media: wave5: Fix SError of kernel panic when closed Jackson.lee
2025-11-05 21:38 ` Brandon Brnich
2025-09-22 5:52 ` [PATCH v5 2/4] media: chips-media: wave5: Fix Null reference while testing fluster Jackson.lee
2025-09-22 5:52 ` [PATCH v5 3/4] media: chips-media: wave5: Add WARN_ON to check if dec_output_info is NULL Jackson.lee
2025-09-22 5:52 ` [PATCH v5 4/4] media: chips-media: wave5: Improve performance of decoder Jackson.lee
2025-09-22 17:32 ` Brandon Brnich
2025-09-22 18:00 ` Nicolas Dufresne
2025-09-24 1:14 ` jackson.lee
2025-09-24 13:20 ` Nicolas Dufresne
2025-09-24 15:06 ` Brandon Brnich [this message]
2025-09-23 0:57 ` jackson.lee
2025-10-27 5:38 ` [PATCH v5 0/4] Performance improvement " jackson.lee
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=76e12732-9a39-409d-aa60-44622fe42ec5@ti.com \
--to=b-brnich@ti.com \
--cc=bob.beckett@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=hverkuil@xs4all.nl \
--cc=jackson.lee@chipsnmedia.com \
--cc=lafley.kim@chipsnmedia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nas.chung@chipsnmedia.com \
--cc=nicolas.dufresne@collabora.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®