From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Charvi Mehta <charvi.mehta@arm.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Rathinavel Sankaralingam <rath.sankaralingam@arm.com>,
Shobhit Pandey <shobhit.pandey@arm.com>
Subject: Re: [RFC PATCH 04/28] media: mali-vpu: initialize decoder format state
Date: Thu, 19 Nov 2026 15:30:51 -0500 [thread overview]
Message-ID: <d1d53edeb358e1bdcd1c262e48074f7f1be276cf.camel@ndufresne.ca> (raw)
In-Reply-To: <20261119153758.1426673-5-charvi.mehta@arm.com>
[-- Attachment #1: Type: text/plain, Size: 16799 bytes --]
Le jeudi 19 novembre 2026 à 15:37 +0000, Charvi Mehta a écrit :
> Describe the H.264 OUTPUT format and YUV420M, NV12M and NV21M CAPTURE
> formats supported by Mali-V76, together with its frame-size limits.
>
> Add source and destination format state to each decoder session and
> initialize both ports from variant defaults. Add the MVE format identifiers
> required by the format descriptors.
>
> Signed-off-by: Charvi Mehta <charvi.mehta@arm.com>
> ---
> drivers/media/platform/arm/mali-vpu/Makefile | 4 +-
> .../platform/arm/mali-vpu/mali-vpu-dec.c | 16 ++++
> .../platform/arm/mali-vpu/mali-vpu-dec.h | 13 +++
> .../platform/arm/mali-vpu/mali-vpu-formats.h | 27 ++++++
> .../arm/mali-vpu/mali-vpu-protocol-def-v3.h | 51 ++++++++++++
> .../platform/arm/mali-vpu/mali-vpu-session.c | 83 +++++++++++++++++++
> .../platform/arm/mali-vpu/mali-vpu-session.h | 18 ++++
> .../arm/mali-vpu/mali-vpu-variant-v76.c | 63 ++++++++++++++
> .../platform/arm/mali-vpu/mali-vpu-variant.h | 30 +++++++
> .../platform/arm/mali-vpu/mali-vpu-vidioc.c | 7 ++
> 10 files changed, 311 insertions(+), 1 deletion(-)
> create mode 100644 drivers/media/platform/arm/mali-vpu/mali-vpu-dec.c
> create mode 100644 drivers/media/platform/arm/mali-vpu/mali-vpu-dec.h
> create mode 100644 drivers/media/platform/arm/mali-vpu/mali-vpu-formats.h
> create mode 100644 drivers/media/platform/arm/mali-vpu/mali-vpu-protocol-def-v3.h
> create mode 100644 drivers/media/platform/arm/mali-vpu/mali-vpu-session.c
>
> diff --git a/drivers/media/platform/arm/mali-vpu/Makefile b/drivers/media/platform/arm/mali-vpu/Makefile
> index e659101bd0eac..0a42c53ae5088 100644
> --- a/drivers/media/platform/arm/mali-vpu/Makefile
> +++ b/drivers/media/platform/arm/mali-vpu/Makefile
> @@ -2,6 +2,8 @@
>
> mali-vpu-objs := mali-vpu-probe.o \
> mali-vpu-variant-v76.o \
> - mali-vpu-vidioc.o
> + mali-vpu-vidioc.o \
> + mali-vpu-session.o \
> + mali-vpu-dec.o
>
> obj-$(CONFIG_VIDEO_MALI_VPU) += mali-vpu.o
> diff --git a/drivers/media/platform/arm/mali-vpu/mali-vpu-dec.c b/drivers/media/platform/arm/mali-vpu/mali-vpu-dec.c
> new file mode 100644
> index 0000000000000..cb6eeee2f04df
> --- /dev/null
> +++ b/drivers/media/platform/arm/mali-vpu/mali-vpu-dec.c
> @@ -0,0 +1,16 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (C) 2026 ARM Limited.
> + */
> +
> +#include "mali-vpu-dec.h"
> +#include "mali-vpu-session.h"
> +#include "mali-vpu-variant.h"
> +
> +void mali_vpu_session_init_dec(struct mali_vpu_session *sess)
> +{
> + const struct mali_vpu_format_caps *variant_fmts = &sess->vpu_dev->variant->fmt_caps;
> +
> + sess->port_src.supported_fmts = variant_fmts->dec_src;
> + sess->port_dst.supported_fmts = variant_fmts->dec_dst;
Why? the variant are constant, you can just read the information from the
variant. Make a getter or point to it.
p.s. is that "port" like in OMX IL?
> +}
> diff --git a/drivers/media/platform/arm/mali-vpu/mali-vpu-dec.h b/drivers/media/platform/arm/mali-vpu/mali-vpu-dec.h
> new file mode 100644
> index 0000000000000..2514c897587c4
> --- /dev/null
> +++ b/drivers/media/platform/arm/mali-vpu/mali-vpu-dec.h
> @@ -0,0 +1,13 @@
> +/* SPDX-License-Identifier: GPL-2.0-only */
> +/*
> + * Copyright (C) 2026 ARM Limited.
> + */
> +
> +#ifndef __MALI_VPU_DEC_H__
> +#define __MALI_VPU_DEC_H__
> +
> +struct mali_vpu_session;
> +
> +void mali_vpu_session_init_dec(struct mali_vpu_session *sess);
> +
> +#endif /* __MALI_VPU_DEC_H__ */
> diff --git a/drivers/media/platform/arm/mali-vpu/mali-vpu-formats.h b/drivers/media/platform/arm/mali-vpu/mali-vpu-formats.h
> new file mode 100644
> index 0000000000000..13031809fdb4d
> --- /dev/null
> +++ b/drivers/media/platform/arm/mali-vpu/mali-vpu-formats.h
> @@ -0,0 +1,27 @@
> +/* SPDX-License-Identifier: GPL-2.0-only */
> +/*
> + * Copyright (C) 2026 ARM Limited.
> + */
> +
> +#ifndef __MALI_VPU_FORMATS_H__
> +#define __MALI_VPU_FORMATS_H__
> +
> +#include <linux/types.h>
> +
> +enum mali_vpu_codec_fmt {
> + MALI_VPU_FORMAT_CODEC_H264,
> +};
> +
> +struct mali_vpu_format_desc {
> + u32 fourcc;
> + u16 mve_frame_fmt;
> + u16 codec_fmt;
> + u32 flags;
> +};
> +
> +struct mali_vpu_format_list {
> + const struct mali_vpu_format_desc *fmts;
> + u32 num_fmts;
> +};
> +
> +#endif /* __MALI_VPU_FORMATS_H__ */
> diff --git a/drivers/media/platform/arm/mali-vpu/mali-vpu-protocol-def-v3.h b/drivers/media/platform/arm/mali-vpu/mali-vpu-protocol-def-v3.h
> new file mode 100644
> index 0000000000000..aed51eec6ca9c
> --- /dev/null
> +++ b/drivers/media/platform/arm/mali-vpu/mali-vpu-protocol-def-v3.h
> @@ -0,0 +1,51 @@
> +/* SPDX-License-Identifier: GPL-2.0-only */
> +/*
> + * Copyright (C) 2026 ARM Limited.
> + */
> +
> +#ifndef __MALI_VPU_PROTOCOL_DEF_V3_H__
> +#define __MALI_VPU_PROTOCOL_DEF_V3_H__
> +
> +/*****************************************************************************
> + *
> + * Communication protocol between the host/driver and the MVE firmware,
> + * the 'host interface'.
> + *
> + * MVE == MALI Video Engine
> + *
> + * Protocol version 3.1
> + *
> + * Note: Message structs may be expanded in the future; the host should
> + * use the 'size' of the message to determine how many bytes to
> + * read from the message queue, rather than a sizeof(struct).
> + *
> + * All multibyte integer fields in the shared-memory interface are little-endian.
> + * The driver supports only little-endian kernels and therefore accesses these
> + * fields in native byte order.
> + *
> + ****************************************************************************/
> +
> + #define MVE_CHROMA_FORMAT_420 (0x1)
> +
> +/* format bitfield: */
> +#define MVE_FORMAT_BF_C (0) /* 3 bits, chroma subsampling */
> +#define MVE_FORMAT_BF_B (4) /* 4 bits, max bitdepth minus 8 */
> +#define MVE_FORMAT_BF_N (8) /* 2 bits, number of planes */
> +#define MVE_FORMAT_BF_V (12) /* 2 bits, format variant */
> +/* formats: */
> +#define MVE_FORMAT_YUV420_I420 ((MVE_CHROMA_FORMAT_420 << MVE_FORMAT_BF_C) | \
> + ((8 - 8) << MVE_FORMAT_BF_B) | \
> + (3 << MVE_FORMAT_BF_N) | \
> + (0 << MVE_FORMAT_BF_V))
> +
> +#define MVE_FORMAT_YUV420_NV12 ((MVE_CHROMA_FORMAT_420 << MVE_FORMAT_BF_C) | \
> + ((8 - 8) << MVE_FORMAT_BF_B) | \
> + (2 << MVE_FORMAT_BF_N) | \
> + (0 << MVE_FORMAT_BF_V))
> +
> +#define MVE_FORMAT_YUV420_NV21 ((MVE_CHROMA_FORMAT_420 << MVE_FORMAT_BF_C) | \
> + ((8 - 8) << MVE_FORMAT_BF_B) | \
> + (2 << MVE_FORMAT_BF_N) | \
> + (1 << MVE_FORMAT_BF_V))
> +
> +#endif /* __MALI_VPU_PROTOCOL_DEF_V3_H__ */
> diff --git a/drivers/media/platform/arm/mali-vpu/mali-vpu-session.c b/drivers/media/platform/arm/mali-vpu/mali-vpu-session.c
> new file mode 100644
> index 0000000000000..9bcb3a73a582e
> --- /dev/null
> +++ b/drivers/media/platform/arm/mali-vpu/mali-vpu-session.c
> @@ -0,0 +1,83 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (C) 2026 ARM Limited.
> + */
> +
> +#include <linux/errno.h>
> +#include <linux/minmax.h>
> +#include <linux/mm.h>
> +#include <linux/string.h>
> +#include <media/v4l2-common.h>
> +
> +#include "mali-vpu-session.h"
> +#include "mali-vpu-dec.h"
> +#include "mali-vpu-variant.h"
> +
> +static int mali_vpu_set_port_fmt(struct mali_vpu_port *port,
> + enum v4l2_buf_type type,
> + u32 width, u32 height)
> +{
> + struct v4l2_pix_format_mplane *pix_mp = &port->curr_fmt.fmt.pix_mp;
> + const struct mali_vpu_format_desc *fmt_default;
> + int ret;
> +
> + if (!port->supported_fmts.fmts || !port->supported_fmts.num_fmts)
> + return -EINVAL;
> +
> + fmt_default = &port->supported_fmts.fmts[0];
> +
> + memset(&port->curr_fmt, 0, sizeof(port->curr_fmt));
> + port->curr_fmt.type = type;
> +
> + if (fmt_default->flags & V4L2_FMT_FLAG_COMPRESSED) {
> + pix_mp->pixelformat = fmt_default->fourcc;
> + pix_mp->num_planes = 1;
> + pix_mp->width = width;
> + pix_mp->height = height;
> + pix_mp->plane_fmt[0].bytesperline = 0;
> +
> + /*
> + * Use one byte per pixel as the default compressed sizeimage,
> + * with a minimum of one page, aligned to a page boundary.
> + */
> + pix_mp->plane_fmt[0].sizeimage = PAGE_ALIGN(max_t(u32, PAGE_SIZE, width * height));
> + } else {
> + ret = v4l2_fill_pixfmt_mp(pix_mp, fmt_default->fourcc, width, height);
> + if (ret)
> + return ret;
I might have to come back to this code once we have TRY/SET_FMT in place,
meanwhile it seems more like a default setting helper then something that will
be part of the ioctl interface.
> + }
> +
> + pix_mp->field = V4L2_FIELD_NONE;
> +
> + return 0;
> +}
> +
> +static int mali_vpu_set_port_defaults(struct mali_vpu_session *sess)
> +{
> + const struct mali_vpu_framesize_caps *fmsz = &sess->vpu_dev->variant->frmsz_caps;
> + int ret;
> +
> + ret = mali_vpu_set_port_fmt(&sess->port_src, V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE,
> + fmsz->width_default, fmsz->height_default);
> + if (ret)
> + return ret;
> +
> + return mali_vpu_set_port_fmt(&sess->port_dst, V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE,
> + fmsz->width_default, fmsz->height_default);
> +}
> +
> +int mali_vpu_session_init(struct mali_vpu_session *sess)
> +{
> + int ret;
> +
> + if (sess->role != MALI_VPU_DECODER)
> + return -EINVAL;
> +
> + mali_vpu_session_init_dec(sess);
> +
> + ret = mali_vpu_set_port_defaults(sess);
> + if (ret)
> + return ret;
> +
> + return 0;
> +}
> diff --git a/drivers/media/platform/arm/mali-vpu/mali-vpu-session.h b/drivers/media/platform/arm/mali-vpu/mali-vpu-session.h
> index 7166c53236f1a..a2778ca496381 100644
> --- a/drivers/media/platform/arm/mali-vpu/mali-vpu-session.h
> +++ b/drivers/media/platform/arm/mali-vpu/mali-vpu-session.h
> @@ -6,21 +6,39 @@
> #ifndef __MALI_VPU_SESSION_H__
> #define __MALI_VPU_SESSION_H__
>
> +#include <linux/videodev2.h>
> #include <media/v4l2-fh.h>
>
> #include "mali-vpu-device.h"
> +#include "mali-vpu-formats.h"
> +
> +/**
> + * struct mali_vpu_port - format state of a src/dst queue in a session.
> + * @curr_fmt: V4L2 format currently configured for the port
> + * @supported_fmts: List of format descriptors supported by the queue.
> + */
> +struct mali_vpu_port {
> + struct v4l2_format curr_fmt;
> + struct mali_vpu_format_list supported_fmts;
> +};
>
> /**
> * struct mali_vpu_session - holds per session state and resources.
> * @vpu_dev: Reference to the parent device structure.
> * @role: Role of this session.
> + * @port_src: Source (OUTPUT) port for this session.
> + * @port_dst: Destination (CAPTURE) port for this session.
> * @fh: V4L2 file handle for this session.
> */
> struct mali_vpu_session {
> struct mali_vpu_dev *vpu_dev;
> enum mali_vpu_session_role role;
> + struct mali_vpu_port port_src;
> + struct mali_vpu_port port_dst;
Ok, its time to comment, src_port and dst_port is a lot easier to read imho.
>
> struct v4l2_fh fh;
> };
>
> +int mali_vpu_session_init(struct mali_vpu_session *sess);
> +
> #endif /* __MALI_VPU_SESSION_H__ */
> diff --git a/drivers/media/platform/arm/mali-vpu/mali-vpu-variant-v76.c b/drivers/media/platform/arm/mali-vpu/mali-vpu-variant-v76.c
> index 36509d6a1c5d5..7b04b51eeedc2 100644
> --- a/drivers/media/platform/arm/mali-vpu/mali-vpu-variant-v76.c
> +++ b/drivers/media/platform/arm/mali-vpu/mali-vpu-variant-v76.c
> @@ -4,18 +4,81 @@
> */
>
> #include <linux/array_size.h>
> +#include <linux/videodev2.h>
>
> +#include "mali-vpu-formats.h"
> +#include "mali-vpu-protocol-def-v3.h"
> #include "mali-vpu-variant.h"
>
> #define MALI_VPU_HW_PID_V76 0x56627
>
> +#define MALI_V76_MAX_FRAME_WIDTH 8192
> +#define MALI_V76_MAX_FRAME_HEIGHT 8192
> +#define MALI_V76_MIN_FRAME_WIDTH 2
> +#define MALI_V76_MIN_FRAME_HEIGHT 2
> +#define MALI_V76_DEFAULT_FRAME_WIDTH 640
> +#define MALI_V76_DEFAULT_FRAME_HEIGHT 480
> +
> static const char * const mali_v76_rst_names[] = {
> "warm",
> };
>
> +static const struct mali_vpu_format_desc mali_v76_dec_src_fmts[] = {
> + {
> + .fourcc = V4L2_PIX_FMT_H264,
> + .mve_frame_fmt = 0,
> + .codec_fmt = MALI_VPU_FORMAT_CODEC_H264,
> + .flags = V4L2_FMT_FLAG_COMPRESSED | V4L2_FMT_FLAG_DYN_RESOLUTION,
> + },
> +};
> +
> +static const struct mali_vpu_format_desc mali_v76_dec_dst_fmts[] = {
> + {
> + .fourcc = V4L2_PIX_FMT_YUV420M,
> + .mve_frame_fmt = MVE_FORMAT_YUV420_I420,
> + .codec_fmt = 0,
> + .flags = 0,
> + },
> + {
> + .fourcc = V4L2_PIX_FMT_NV12M,
> + .mve_frame_fmt = MVE_FORMAT_YUV420_NV12,
> + .codec_fmt = 0,
> + .flags = 0,
> + },
> + {
> + .fourcc = V4L2_PIX_FMT_NV21M,
> + .mve_frame_fmt = MVE_FORMAT_YUV420_NV21,
> + .codec_fmt = 0,
> + .flags = 0,
> + },
> +};
> +
> const struct mali_vpu_variant mali_vpu_v76_variant = {
> .expected_hw_pid = MALI_VPU_HW_PID_V76,
>
> .rst_names = mali_v76_rst_names,
> .num_rsts = ARRAY_SIZE(mali_v76_rst_names),
> +
> + .fmt_caps = {
> + .dec_src = {
> + .fmts = mali_v76_dec_src_fmts,
> + .num_fmts = ARRAY_SIZE(mali_v76_dec_src_fmts),
> + },
> + .dec_dst = {
> + .fmts = mali_v76_dec_dst_fmts,
> + .num_fmts = ARRAY_SIZE(mali_v76_dec_dst_fmts),
> + },
> + },
> + .frmsz_caps = {
> + .stepwise = {
> + .min_width = MALI_V76_MIN_FRAME_WIDTH,
> + .max_width = MALI_V76_MAX_FRAME_WIDTH,
> + .step_width = 2,
> + .min_height = MALI_V76_MIN_FRAME_HEIGHT,
> + .max_height = MALI_V76_MAX_FRAME_HEIGHT,
> + .step_height = 2,
> + },
Are you sure this will be the same for all codecs and all formats?
> + .width_default = MALI_V76_DEFAULT_FRAME_WIDTH,
> + .height_default = MALI_V76_DEFAULT_FRAME_HEIGHT,
> + },
> };
> diff --git a/drivers/media/platform/arm/mali-vpu/mali-vpu-variant.h b/drivers/media/platform/arm/mali-vpu/mali-vpu-variant.h
> index dadfd686275db..a46c25a94f18b 100644
> --- a/drivers/media/platform/arm/mali-vpu/mali-vpu-variant.h
> +++ b/drivers/media/platform/arm/mali-vpu/mali-vpu-variant.h
> @@ -7,17 +7,47 @@
> #define __MALI_VPU_VARIANT_H__
>
> #include <linux/types.h>
> +#include <linux/videodev2.h>
> +
> +#include "mali-vpu-formats.h"
> +
> +/**
> + * struct mali_vpu_framesize_caps - Variant-specific frame size capability.
> + * @stepwise: Stepwise frame size limits and increments supported by the hardware.
> + * @width_default: Default width used when userspace does not request one.
> + * @height_default: Default height used when userspace does not request one.
> + */
> +struct mali_vpu_framesize_caps {
> + struct v4l2_frmsize_stepwise stepwise;
> + u32 width_default;
> + u32 height_default;
> +};
> +
> +/**
> + * struct mali_vpu_format_caps - Pixel/coded format capability tables.
> + * @dec_src: List of formats supported on decoder OUTPUT queue (compressed bitstream in).
> + * @dec_dst: List of formats supported on decoder CAPTURE queue (decoded raw frames).
> + */
> +struct mali_vpu_format_caps {
> + const struct mali_vpu_format_list dec_src;
> + const struct mali_vpu_format_list dec_dst;
Strange naming, perhaps src_formats/dst_formats?
> +};
>
> /**
> * struct mali_vpu_variant - Variant-specific hardware capability descriptor.
> * @rst_names: Array of reset control names for this variant.
> * @num_rsts: Number of reset controls for this variant.
> * @expected_hw_pid: Expected hardware product ID read from the version register.
> + * @fmt_caps: Format capability tables for encode/decode paths.
> + * @frmsz_caps: Frame dimension limits and defaults.
> */
> struct mali_vpu_variant {
> const char * const *rst_names;
> unsigned int num_rsts;
> u32 expected_hw_pid;
> +
> + struct mali_vpu_format_caps fmt_caps;
> + struct mali_vpu_framesize_caps frmsz_caps;
> };
>
> extern const struct mali_vpu_variant mali_vpu_v76_variant;
> diff --git a/drivers/media/platform/arm/mali-vpu/mali-vpu-vidioc.c b/drivers/media/platform/arm/mali-vpu/mali-vpu-vidioc.c
> index 7a169b7b14bf3..13468c6baba76 100644
> --- a/drivers/media/platform/arm/mali-vpu/mali-vpu-vidioc.c
> +++ b/drivers/media/platform/arm/mali-vpu/mali-vpu-vidioc.c
> @@ -37,8 +37,15 @@ static int mali_vpu_open(struct file *filp)
> v4l2_fh_init(&sess->fh, vdev);
> v4l2_fh_add(&sess->fh, filp);
>
> + ret = mali_vpu_session_init(sess);
> + if (ret)
> + goto err_v4l2_fh_deinit;
> +
> return 0;
>
> +err_v4l2_fh_deinit:
> + v4l2_fh_del(&sess->fh, filp);
> + v4l2_fh_exit(&sess->fh);
> err_free_sess:
> kfree(sess);
> return ret;
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-11-19 20:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 15:37 [RFC PATCH 00/28] media: add arm Mali-V76 video decoder driver Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 01/28] dt-bindings: media: add Arm Mali-V76 VPU Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 02/28] media: mali-vpu: add Mali VPU platform driver Charvi Mehta
2026-11-19 20:04 ` Nicolas Dufresne
2026-11-19 15:37 ` [RFC PATCH 03/28] media: mali-vpu: register V4L2 decoder device and add querycap ioctl Charvi Mehta
2026-11-19 20:10 ` Nicolas Dufresne
2026-11-19 15:37 ` [RFC PATCH 04/28] media: mali-vpu: initialize decoder format state Charvi Mehta
2026-11-19 20:30 ` Nicolas Dufresne [this message]
2026-11-19 15:37 ` [RFC PATCH 05/28] media: mali-vpu: add V4L2 mem2mem and VB2 queue support Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 06/28] media: mali-vpu: implement format query ioctls Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 07/28] media: mali-vpu: implement TRY_FMT and S_FMT ioctls Charvi Mehta
2026-11-19 20:44 ` Nicolas Dufresne
2026-11-19 15:37 ` [RFC PATCH 08/28] media: mali-vpu: register V76 decoder controls and introduce UAPI controls Charvi Mehta
2026-11-19 21:06 ` Nicolas Dufresne
2026-11-19 15:37 ` [RFC PATCH 09/28] media: mali-vpu: add MMU software page table manager Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 10/28] media: mali-vpu: add firmware cache infrastructure Charvi Mehta
2026-11-19 21:34 ` Nicolas Dufresne
2026-11-19 15:37 ` [RFC PATCH 11/28] media: mali-vpu: load firmware for decoder sessions Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 12/28] media: mali-vpu: prepare firmware address space Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 13/28] media: mali-vpu: add firmware message transport Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 14/28] media: mali-vpu: route decoder controls to firmware Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 15/28] media: mali-vpu: handle firmware RPC requests Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 16/28] media: mali-vpu: add LSID hardware support Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 17/28] media: mali-vpu: add single session scheduler Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 18/28] media: mali-vpu: handle firmware interrupts Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 19/28] media: mali-vpu: start decoder firmware through LSID scheduling Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 20/28] media: mali-vpu: implement vb2 buffer queue handling Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 21/28] media: mali-vpu: handle firmware buffer exchange Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 22/28] media: mali-vpu: handle fatal firmware error Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 23/28] media: mali-vpu: propagate buffer metadata Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 24/28] media: mali-vpu: add decoder EOS and DRC handling Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 25/28] media: mali-vpu: handle firmware buffer parameters Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 26/28] media: mali-vpu: handle firmware event responses Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 27/28] media: mali-vpu: add stateful decoder state machine Charvi Mehta
2026-11-19 15:37 ` [RFC PATCH 28/28] media: MAINTAINERS: add Arm Mali-V76 VPU driver Charvi Mehta
2026-11-19 19:44 ` [RFC PATCH 00/28] media: add arm Mali-V76 video decoder driver 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=d1d53edeb358e1bdcd1c262e48074f7f1be276cf.camel@ndufresne.ca \
--to=nicolas@ndufresne.ca \
--cc=charvi.mehta@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rath.sankaralingam@arm.com \
--cc=robh@kernel.org \
--cc=shobhit.pandey@arm.com \
--cc=vincenzo.frascino@arm.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
all inboxes | Powered by JetHome®