From: Devarsh Thakkar <devarsht@ti.com>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>,
"jackson.lee" <jackson.lee@chipsnmedia.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"sebastian.fricke@collabora.com" <sebastian.fricke@collabora.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
Nas Chung <nas.chung@chipsnmedia.com>,
"lafley.kim" <lafley.kim@chipsnmedia.com>,
"b-brnich@ti.com" <b-brnich@ti.com>,
"Luthra, Jai" <j-luthra@ti.com>, Vibhore <vibhore@ti.com>,
Dhruva Gole <d-gole@ti.com>, Aradhya <a-bhatia1@ti.com>,
"Raghavendra, Vignesh" <vigneshr@ti.com>
Subject: Re: [RESEND PATCH v6 2/4] media: chips-media: wave5: Support runtime suspend/resume
Date: Fri, 21 Jun 2024 18:01:59 +0530 [thread overview]
Message-ID: <147fddd4-0f73-0546-b73e-d8e2326bfb2a@ti.com> (raw)
In-Reply-To: <07d56a690d5fed16082e73c5565b67777e31494a.camel@collabora.com>
Hi Nicolas,
On 20/06/24 23:02, Nicolas Dufresne wrote:
> Le jeudi 20 juin 2024 à 19:50 +0530, Devarsh Thakkar a écrit :
[..]
> Imagine that userspace is going gapless playback, if you have a lets say
30ms on
> forced suspend cycle due to close/open of the decoder instance, it won't
> actually endup gapless. The delay will ensure that we only suspend when needed.
>
Shouldn't the applications doing gapless playback avoid frequent open/close of
the decoder instance too as it will add up re-instantiation (initializing hw,
allocating buffers) and cleanup (de-initialization and freeing up of buffers)
delay for each open/close respectively ? Even in case of scenario where
resolution of next stream is different than previous, I guess the application
can still hold up the file handle and do the necessary setup (stream
off/stream on/REQBUFS etc) required for re-initialization ?
Regards
Devarsh
next prev parent reply other threads:[~2024-06-21 12:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 10:48 [RESEND PATCH v6 0/4] Add features to an existing driver Jackson.lee
2024-06-17 10:48 ` [RESEND PATCH v6 1/4] media: chips-media: wave5: Support SPS/PPS generation for each IDR Jackson.lee
2024-06-17 10:48 ` [RESEND PATCH v6 2/4] media: chips-media: wave5: Support runtime suspend/resume Jackson.lee
2024-06-19 13:00 ` Devarsh Thakkar
2024-06-19 23:56 ` jackson.lee
2024-06-20 0:11 ` jackson.lee
2024-06-20 9:35 ` Devarsh Thakkar
2024-06-20 14:05 ` Nicolas Dufresne
2024-06-20 14:20 ` Devarsh Thakkar
2024-06-20 17:32 ` Nicolas Dufresne
2024-06-21 0:30 ` jackson.lee
2024-06-21 11:55 ` Devarsh Thakkar
2024-06-21 12:45 ` jackson.lee
2024-06-21 12:31 ` Devarsh Thakkar [this message]
2024-07-15 17:01 ` Nicolas Dufresne
2024-07-12 6:10 ` jackson.lee
2024-07-15 17:05 ` Nicolas Dufresne
2024-07-16 1:02 ` jackson.lee
2024-06-20 14:03 ` Nicolas Dufresne
2024-06-20 14:52 ` Devarsh Thakkar
2024-06-20 15:24 ` Nicolas Dufresne
2024-06-21 7:36 ` jackson.lee
2024-06-20 15:20 ` Nicolas Dufresne
2024-06-17 10:48 ` [RESEND PATCH v6 3/4] media: chips-media: wave5: Use helpers to calculate bytesperline and sizeimage Jackson.lee
2024-06-17 10:48 ` [RESEND PATCH v6 4/4] media: chips-media: wave5: Support YUV422 raw pixel-formats on the encoder Jackson.lee
2024-06-18 9:29 ` [RESEND PATCH v6 0/4] Add features to an existing driver Sebastian Fricke
2024-06-19 5:38 ` 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=147fddd4-0f73-0546-b73e-d8e2326bfb2a@ti.com \
--to=devarsht@ti.com \
--cc=a-bhatia1@ti.com \
--cc=b-brnich@ti.com \
--cc=d-gole@ti.com \
--cc=hverkuil@xs4all.nl \
--cc=j-luthra@ti.com \
--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 \
--cc=sebastian.fricke@collabora.com \
--cc=vibhore@ti.com \
--cc=vigneshr@ti.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