From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Emmanuel Gil Peyrot <linkmauve@linkmauve.fr>,
Dan Carpenter <dan.carpenter@linaro.org>
Cc: linux-sunxi@lists.linux.dev, Maxime Ripard <mripard@kernel.org>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Chen-Yu Tsai <wens@csie.org>,
Samuel Holland <samuel@sholland.org>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/4] media: cedrus: Don't require requests for all codecs
Date: Thu, 20 Feb 2025 18:34:52 +0100 [thread overview]
Message-ID: <2235304.C4sosBPzcN@jernej-laptop> (raw)
In-Reply-To: <b3ab99a1-2e72-4b7e-8569-f7fe9beb3018@suswa.mountain>
Dne sreda, 31. julij 2024 ob 18:56:15 Srednjeevropski standardni čas je Dan Carpenter napisal(a):
> On Wed, Jul 31, 2024 at 06:44:14PM +0200, Emmanuel Gil Peyrot wrote:
> > From: Jernej Skrabec <jernej.skrabec@gmail.com>
> >
> > JPEG decoding doesn’t need it currently.
> >
> > Signed-off-by: Jernej Skrabec <jernej.skrabec@gmail.com>
> > ---
>
> Does this change have an effect on runtime?
Ideally, driver should allow only JPEG format to be used without request api.
Other codecs still require it (decoding doesn't work properly without it).
Best regards,
Jernej
>
> regards,
> dan carpenter
>
>
>
prev parent reply other threads:[~2025-02-20 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 16:44 [PATCH 0/4] media: cedrus: Add a JPEG decoder Emmanuel Gil Peyrot
2024-07-31 16:44 ` [PATCH 1/4] media: cedrus: Setup secondary output formats Emmanuel Gil Peyrot
2024-07-31 16:44 ` [PATCH 2/4] media: cedrus: Add JPEG decoder Emmanuel Gil Peyrot
2025-02-13 17:12 ` Sebastian Fricke
2025-02-20 17:32 ` Jernej Škrabec
2024-07-31 16:44 ` [PATCH 3/4] media: cedrus: Enable JPEG decoding in various variants Emmanuel Gil Peyrot
2024-07-31 16:44 ` [PATCH 4/4] media: cedrus: Don't require requests for all codecs Emmanuel Gil Peyrot
2024-07-31 16:56 ` Dan Carpenter
2025-02-20 17:34 ` Jernej Škrabec [this message]
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=2235304.C4sosBPzcN@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linkmauve@linkmauve.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-sunxi@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=samuel@sholland.org \
--cc=wens@csie.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