linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: "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>,
	 "b-brnich@ti.com"	 <b-brnich@ti.com>,
	"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
	Nas Chung	 <nas.chung@chipsnmedia.com>
Subject: Re: [PATCH v2 2/7] media: chips-media: wave5: Improve performance of decoder
Date: Thu, 05 Jun 2025 09:28:37 -0400	[thread overview]
Message-ID: <8c6316d2d00287e96bc2ad5d27c8de37f990b7e5.camel@collabora.com> (raw)
In-Reply-To: <SE1P216MB1303F7ADAC83F6CE312C5CA3ED6FA@SE1P216MB1303.KORP216.PROD.OUTLOOK.COM>

Hi,

Le jeudi 05 juin 2025 à 04:50 +0000, jackson.lee a écrit :
> > So my question is, is there a way to know, at CMD_STOP call, that the HW
> > has gone idle, and that no more events will allow handling the EOS case?
> > 
> > Nicolas
> 
> 
> Thanks for your reply.	
> 
> Now there is only one thing to know if there is more events or not to handle the EOS case.
> It is that driver sends DEC_PIC command to VPU continuously until display index is -2(it means EOS) from VPU.
> VPU should trigger interrupts to get display index from the finish_decode function.
> So we have to run device_run to send DEC_PIC command.

What don't want to see is a loop where we do:

	device_run()
		finish_job()
			device_run()
				finish_job()
					....

What I see now, is that we simply bang on the trigger until it completes, which
is very wasteful in power and CPU time. In your next version, make sure to
find a mitigation to that active loop, and document it please.

Nicolas

  reply	other threads:[~2025-06-05 13:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22  7:25 [PATCH v2 0/7] Performance improvement of decoder Jackson.lee
2025-05-22  7:26 ` [PATCH v2 1/7] media: chips-media: wave5: Fix Null reference while testing fluster Jackson.lee
2025-05-23 17:20   ` Nicolas Dufresne
2025-05-27  4:05     ` jackson.lee
2025-05-27 12:57       ` Nicolas Dufresne
2025-05-22  7:26 ` [PATCH v2 2/7] media: chips-media: wave5: Improve performance of decoder Jackson.lee
2025-05-23 17:39   ` Nicolas Dufresne
2025-05-27  4:58     ` jackson.lee
2025-05-28 13:46       ` Nicolas Dufresne
2025-06-04  4:09         ` jackson.lee
2025-06-04 13:47           ` Nicolas Dufresne
2025-06-05  4:50             ` jackson.lee
2025-06-05 13:28               ` Nicolas Dufresne [this message]
2025-06-09  8:47                 ` jackson.lee
2025-05-30 14:33       ` Nicolas Dufresne
2025-05-22  7:26 ` [PATCH v2 3/7] media: chips-media: wave5: Fix not to be closed Jackson.lee
2025-05-22  7:26 ` [PATCH v2 4/7] media: chips-media: wave5: Use spinlock whenever statue is changed Jackson.lee
2025-05-23 17:41   ` Nicolas Dufresne
2025-05-27  5:02     ` jackson.lee
2025-05-28 13:49       ` Nicolas Dufresne
2025-05-22  7:26 ` [PATCH v2 5/7] media: chips-media: wave5: Fix not to free resources normally when instance was destroyed Jackson.lee
2025-05-23 17:42   ` Nicolas Dufresne
2025-05-27  5:04     ` jackson.lee
2025-05-22  7:26 ` [PATCH v2 6/7] media: chips-media: wave5: Reduce high CPU load Jackson.lee
2025-05-23 17:43   ` Nicolas Dufresne
2025-05-27  5:05     ` jackson.lee
2025-05-22  7:26 ` [PATCH v2 7/7] media: chips-media: wave5: Fix SError of kernel panic when closed Jackson.lee
2025-05-23 17:48   ` Nicolas Dufresne
2025-05-27  5:07     ` 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=8c6316d2d00287e96bc2ad5d27c8de37f990b7e5.camel@collabora.com \
    --to=nicolas.dufresne@collabora.com \
    --cc=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 \
    /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;
as well as URLs for NNTP newsgroup(s).