From: "Ezequiel Garcia" <ezequiel@collabora.com>
To: "Hans Verkuil" <hverkuil@xs4all.nl>
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: Re: [RFC] Moving codec drivers out of staging
Date: Sat, 01 May 2021 13:43:48 +0100 [thread overview]
Message-ID: <49b1-608d4d00-2b-62afdf80@101971638> (raw)
In-Reply-To: <9bde97ea-aea7-3db4-407b-2ac9e13a9a28@xs4all.nl>
On Friday, April 30, 2021 03:48 -03, Hans Verkuil <hverkuil@xs4all.nl> wrote:
> 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.
>
Hantro HEVC patches are posted :-)
> Same question for rkvdec, that too looks ready to move over to mainline.
>
These drivers are used in production, so moving out of staging sounds great.
Note that we have some patches for Hantro (SAMA5 support and HEVC support). I wouldn't want to ask a rebase for these, so can we first merge them and then move? It all sounds doable in the next cycle.
Thanks a lot!
Ezequiel
prev parent reply other threads:[~2021-05-01 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 6:48 [RFC] Moving codec drivers out of staging Hans Verkuil
2021-04-30 18:55 ` Jernej Škrabec
2021-05-01 12:43 ` Ezequiel Garcia [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=49b1-608d4d00-2b-62afdf80@101971638 \
--to=ezequiel@collabora.com \
--cc=daniel.almeida@collabora.com \
--cc=hverkuil@xs4all.nl \
--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).