public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
To: liujianfeng1994@gmail.com
Cc: nicolas@ndufresne.ca, conor+dt@kernel.org,
	devicetree@vger.kernel.org, elezegarcia@gmail.com,
	"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
	"Heiko Stübner" <heiko@sntech.de>,
	knaerzche@gmail.com, krzysztof.kozlowski+dt@linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	mchehab@kernel.org, "Philipp Zabel" <p.zabel@pengutronix.de>,
	"Rob Herring" <robh+dt@kernel.org>,
	sfr@canb.auug.org.au, amazingfate <liujianfeng1994@gmail.com>
Subject: Re: [PATCH v3 0/2] [v3]Add hantro g1 video decoder support for RK3588
Date: Thu, 18 Jan 2024 14:53:47 +0100	[thread overview]
Message-ID: <2CFF2A39-6416-4599-AD32-E99EF95F5A36@gmail.com> (raw)
In-Reply-To: <20240118113051.10773-1-liujianfeng1994@gmail.com>


> Wiadomość napisana przez amazingfate <liujianfeng1994@gmail.com> w dniu 18.01.2024, o godz. 12:30:
> 
> Before rkvdec2 launching mainline

Ooooo - is there concrete plan for this?

Asking as imho rk35xx can be really nice multimedia soc.

Can be…. but is not due current lack of hevc/vp9 hw decode in mainline due lack of rkvdec2 support
This seems to be clear blocker for many multimedia use cases :-(

Having rkvdec2 support via v4l2_request in mainline imho will make rk35xx killer soc for multimedia….

ps: rkvdec support seems available since years on mainline and works well.
So maybe rkvdec code base can be basis to gradually added support for rkvdec2?
   



_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2024-01-18 13:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-31 15:11 [PATCH v3 0/2] [v3]Add hantro g1 video decoder support for RK3588 Jianfeng Liu
2023-12-31 15:11 ` [PATCH v3 1/2] arm64: dts: rockchip: Add Hantro G1 VPU " Jianfeng Liu
2024-01-17 19:13   ` Nicolas Dufresne
2024-01-18  8:06     ` amazingfate
2024-01-18 21:44       ` Nicolas Dufresne
2023-12-31 15:11 ` [PATCH v3 2/2] dt-bindings: media: rockchip-vpu: Add rk3588 vpu compatible string Jianfeng Liu
2024-01-01 13:58   ` Conor Dooley
2024-03-15 12:22   ` Heiko Stübner
2024-03-15 12:45     ` Jianfeng Liu
2024-01-17 19:16 ` [PATCH v3 0/2] [v3]Add hantro g1 video decoder support for RK3588 Nicolas Dufresne
2024-01-17 21:12   ` Heiko Stübner
2024-01-18 11:30   ` amazingfate
2024-01-18 13:53     ` Piotr Oniszczuk [this message]
2024-01-18 21:51       ` Nicolas Dufresne

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=2CFF2A39-6416-4599-AD32-E99EF95F5A36@gmail.com \
    --to=piotr.oniszczuk@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=elezegarcia@gmail.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=heiko@sntech.de \
    --cc=knaerzche@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=liujianfeng1994@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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