linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: "Linux Media Mailing List" <linux-media@vger.kernel.org>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Jernej Škrabec" <jernej.skrabec@siol.net>,
	"Nicolas Dufresne" <nicolas@ndufresne.ca>,
	"Jonas Karlman" <jonas@kwiboo.se>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>
Subject: [RFC] Moving codec drivers out of staging
Date: Fri, 30 Apr 2021 08:48:45 +0200	[thread overview]
Message-ID: <9bde97ea-aea7-3db4-407b-2ac9e13a9a28@xs4all.nl> (raw)

Hi all,

I just posted the pull request to move the MPEG-2 stateless codec API out of staging,
so after that only the HEVC stateless codec API is still in staging.

I think it is time to move the stateless codec drivers out of staging, and use a
kernel config option to enable/disable the staging HEVC API:

---------------------------------------------------------------------------
diff --git a/drivers/staging/media/Kconfig b/drivers/staging/media/Kconfig
index ca59986b20f8..faa2fbeb29f0 100644
--- a/drivers/staging/media/Kconfig
+++ b/drivers/staging/media/Kconfig
@@ -22,6 +22,15 @@ if STAGING_MEDIA && MEDIA_SUPPORT
 # Please keep them in alphabetic order
 source "drivers/staging/media/atomisp/Kconfig"

+menuconfig STAGING_MEDIA_HEVC
+	bool "Support HEVC in stateless codec drivers"
+	default n
+	help
+	  This option allows you to enable support for the HEVC codec in
+	  stateless codec drivers. The public API for HEVC is still under
+	  development and is guaranteed to change in the future, so this
+	  option should not be enabled unless you know what you are doing!
+
 source "drivers/staging/media/hantro/Kconfig"

 source "drivers/staging/media/imx/Kconfig"
---------------------------------------------------------------------------

Is there any reason why hantro cannot be moved to mainline? It doesn't
support HEVC, so it can just be moved. Ezequiel, can you check the TODO?
I don't think there is anything there that prevents moving it.

Same question for rkvdec, that too looks ready to move over to mainline.

Same question for the cedrus driver, that too should be ready to move.
It only needs to be patched so that it depends on the suggested kernel option
above. Everything in the TODO is done, so there is no reason to keep it
in staging.

Regards,

	Hans

             reply	other threads:[~2021-04-30  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30  6:48 Hans Verkuil [this message]
2021-04-30 18:55 ` [RFC] Moving codec drivers out of staging Jernej Škrabec
2021-05-01 12:43 ` Ezequiel Garcia

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=9bde97ea-aea7-3db4-407b-2ac9e13a9a28@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=daniel.almeida@collabora.com \
    --cc=ezequiel@collabora.com \
    --cc=jernej.skrabec@siol.net \
    --cc=jonas@kwiboo.se \
    --cc=linux-media@vger.kernel.org \
    --cc=mripard@kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=paul.kocialkowski@bootlin.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).