[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240412151515.837824-1-linkmauve@linkmauve.fr>
Date: Fri, 12 Apr 2024 17:15:09 +0200
From: Emmanuel Gil Peyrot <linkmauve@...kmauve.fr>
To: linux-kernel@...r.kernel.org
Cc: Emmanuel Gil Peyrot <linkmauve@...kmauve.fr>,
Ezequiel Garcia <ezequiel@...guardiasur.com.ar>,
Philipp Zabel <p.zabel@...gutronix.de>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Heiko Stuebner <heiko@...ech.de>,
Joerg Roedel <joro@...tes.org>,
Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Sebastian Reichel <sebastian.reichel@...labora.com>,
Cristian Ciocaltea <cristian.ciocaltea@...labora.com>,
Dragan Simic <dsimic@...jaro.org>,
Shreeya Patel <shreeya.patel@...labora.com>,
Chris Morgan <macromorgan@...mail.com>,
Andy Yan <andy.yan@...k-chips.com>,
Nicolas Frattaroli <frattaroli.nicolas@...il.com>,
linux-media@...r.kernel.org,
linux-rockchip@...ts.infradead.org,
devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
iommu@...ts.linux.dev
Subject: [PATCH v3 0/2] Enable JPEG encoding on rk3588
Only the JPEG encoder is available for now, although there are patches
for the undocumented VP8 encoder floating around[0].
This has been tested on a rock-5b, resulting in four /dev/video*
encoders. The userspace program I’ve been using to test them is
Onix[1], using the jpeg-encoder example, it will pick one of these four
at random (but displays the one it picked):
% ffmpeg -i <input image> -pix_fmt yuvj420p temp.yuv
% jpeg-encoder temp.yuv <width> <height> NV12 <quality> output.jpeg
[0] https://patchwork.kernel.org/project/linux-rockchip/list/?series=789885
[1] https://crates.io/crates/onix
Changes since v2:
- Only expose a single VEPU121, since the driver doesn’t yet support
exposing them all as a single video node to userspace.
Changes since v1:
- Dropped patches 1 and 4.
- Use the proper compatible form, since this device should be fully
compatible with the VEPU of rk356x.
- Describe where the VEPU121 name comes from, and list other encoders
and decoders present in this SoC.
- Properly test the device tree changes, I previously couldn’t since I
was using a too recent version of python-jsonschema…
Emmanuel Gil Peyrot (2):
media: dt-binding: media: Document rk3588’s VEPU121
arm64: dts: rockchip: Add one VEPU121 to rk3588
.../bindings/media/rockchip,rk3568-vepu.yaml | 8 +++--
arch/arm64/boot/dts/rockchip/rk3588s.dtsi | 29 +++++++++++++++++++
2 files changed, 35 insertions(+), 2 deletions(-)
--
2.44.0
Powered by blists - more mailing lists