linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: "Linux Media Mailing List" <linux-media@vger.kernel.org>,
	"Nicolas Dufresne" <nicolas.dufresne@collabora.com>,
	"Jonas Karlman" <jonas@kwiboo.se>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Jernej Škrabec" <jernej.skrabec@gmail.com>
Subject: Re: RFC: cedrus: time to more to mainline?
Date: Tue, 7 Nov 2023 21:08:28 +0100	[thread overview]
Message-ID: <ZUqZPJW9JNuZPpLX@aptenodytes> (raw)
In-Reply-To: <5c93488e-3949-4bb3-bdff-0a60b4586183@xs4all.nl>

[-- Attachment #1: Type: text/plain, Size: 2462 bytes --]

Hans,

On Tue 07 Nov 23, 16:00, Hans Verkuil wrote:
> On 07/11/2023 15:25, Paul Kocialkowski wrote:
> > Hi Hans,
> > 
> > On Tue 07 Nov 23, 14:54, Hans Verkuil wrote:
> >> Looking at the cedrus TODO:
> >>
> >> Before this stateless decoder driver can leave the staging area:
> >> * The Request API needs to be stabilized;
> >> * The codec-specific controls need to be thoroughly reviewed to ensure they
> >>   cover all intended uses cases;
> >> * Userspace support for the Request API needs to be reviewed;
> >> * Another stateless decoder driver should be submitted;
> >> * At least one stateless encoder driver should be submitted.
> >>
> >> I would say that all items are done, except for the last item.
> >>
> >> But this is a decoder driver, so I'm not sure why the TODO would mention
> >> something about encoders.
> > 
> > I agree. This didn't prevent the hantro driver form being unstaged anyway.
> > 
> >> Anything else that needs to be done before it can be moved out of staging?
> > 
> > I'm actually working on a big rework of the driver, because its architecture
> > is vastly sub-optimal and overall very messy. This is in particular needed for
> > the work to support H.264 encoding.
> > 
> > The plan for now is to publish this work in a downstream repository (at Bootlin)
> > since we don't yet have a uAPI for encoding. The rework is also not split into
> > nice transition commits but it's instead a big all-in-one commit for the moment.
> > 
> > However I would like to see this rework hit mainline after the publication of
> > the encoding work, because it's a much needed cleanup for the decode side too.
> > I will of course split it into nice commits at that point.
> > 
> > So I'm not sure whether this conflicts with unstaging or not. It could make
> > sense to wait until the rework is achieved to unstage, but I would also be fine
> > with unstaging first. It would just make me slightly happier to bring big
> > changes to a staging driver instead of a fully-merged one.
> > 
> > What do you think?
> 
> Fine with me, but I would appreciate it if you can post a patch updating the TODO
> file. That's really out of date, and you can mention the rework you are doing.

Great, I've just sent out a patch which replaces the current TODO with a
description of the rework.

Thanks,

Paul

-- 
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2023-11-07 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 13:54 RFC: cedrus: time to more to mainline? Hans Verkuil
2023-11-07 14:25 ` Paul Kocialkowski
2023-11-07 15:00   ` Hans Verkuil
2023-11-07 20:08     ` Paul Kocialkowski [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=ZUqZPJW9JNuZPpLX@aptenodytes \
    --to=paul.kocialkowski@bootlin.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-media@vger.kernel.org \
    --cc=mripard@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).