[v2,00/34] Qualcomm video encoder and decoder driver
| Message ID | 1702899149-21321-1-git-send-email-quic_dikshita@quicinc.com (mailing list archive) |
|---|---|
| Headers |
Received: from ny.mirrors.kernel.org ([147.75.199.223])
by www.linuxtv.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.92)
(envelope-from
<linux-media+bounces-2557-patchwork=linuxtv.org@vger.kernel.org>)
id 1rFBu1-00Cv4V-Hd
for patchwork@linuxtv.org; Mon, 18 Dec 2023 11:35:18 +0000
Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org
[52.25.139.140])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ny.mirrors.kernel.org (Postfix) with ESMTPS id 6F4071C226A2
for <patchwork@linuxtv.org>; Mon, 18 Dec 2023 11:35:14 +0000 (UTC)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
by smtp.subspace.kernel.org (Postfix) with ESMTP id 7156C1CAAC;
Mon, 18 Dec 2023 11:33:22 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org;
dkim=pass (2048-bit key) header.d=quicinc.com header.i=@quicinc.com
header.b="eqnwoNUq"
X-Original-To: linux-media@vger.kernel.org
Received: from mx0b-0031df01.pphosted.com (mx0b-0031df01.pphosted.com
[205.220.180.131])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5FCA81B27A;
Mon, 18 Dec 2023 11:33:19 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org;
dmarc=pass (p=none dis=none) header.from=quicinc.com
Authentication-Results: smtp.subspace.kernel.org;
spf=pass smtp.mailfrom=qualcomm.com
Received: from pps.filterd (m0279870.ppops.net [127.0.0.1])
by mx0a-0031df01.pphosted.com (8.17.1.24/8.17.1.24) with ESMTP id
3BIArrZX007847;
Mon, 18 Dec 2023 11:33:09 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=
from:to:cc:subject:date:message-id; s=qcppdkim1; bh=BVqhlyZ4naps
/Vtfgkn5TdPw6rNLybDqwsKTscaywgw=; b=eqnwoNUqf0AySpz/62PaDBOBqcOd
jX6B05EeDU33wByQ5cY9KACEpA1Q4sEEAEvhzltAqHmAlsLVtbbJHwbIerDuZJKE
8VK8k1SaWuNMyOGlugyrcRBFPFMP2bs7a5oPzhBz6T7nXsKgNThXu97K9KDbQ4bo
FJCG1jjY9GGlZi7XYy3DVDDYkubvoaYW/iynSp8nngKcg+uO0DmyEEv0lva28J5A
NL6E8L2CxosT1C5F+nnyfRUQo+/Xrrv6/N1YvFp9RAj05lKB1o432fd1RHq8trn8
AlvDzO5LyOwOH+0ZODATGwvbHeWQWxwzkFzODy5IjDH+w1NSFVCwQMD8Ig==
Received: from apblrppmta01.qualcomm.com
(blr-bdr-fw-01_GlobalNAT_AllZones-Outside.qualcomm.com [103.229.18.19])
by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3v2m49g5gv-1
(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT);
Mon, 18 Dec 2023 11:33:09 +0000 (GMT)
Received: from pps.filterd (APBLRPPMTA01.qualcomm.com [127.0.0.1])
by APBLRPPMTA01.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTP id
3BIBX5KT029944;
Mon, 18 Dec 2023 11:33:05 GMT
Received: from pps.reinject (localhost [127.0.0.1])
by APBLRPPMTA01.qualcomm.com (PPS) with ESMTP id 3v14ykyyg7-1;
Mon, 18 Dec 2023 11:33:05 +0000
Received: from APBLRPPMTA01.qualcomm.com (APBLRPPMTA01.qualcomm.com
[127.0.0.1])
by pps.reinject (8.17.1.5/8.17.1.5) with ESMTP id 3BIBVmqp028240;
Mon, 18 Dec 2023 11:33:05 GMT
Received: from hu-sgudaval-hyd.qualcomm.com (hu-dikshita-hyd.qualcomm.com
[10.213.110.13])
by APBLRPPMTA01.qualcomm.com (PPS) with ESMTP id 3BIBX59H029907;
Mon, 18 Dec 2023 11:33:05 +0000
Received: by hu-sgudaval-hyd.qualcomm.com (Postfix, from userid 347544)
id 1F56E22AB; Mon, 18 Dec 2023 17:03:04 +0530 (+0530)
From: Dikshita Agarwal <quic_dikshita@quicinc.com>
To: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
stanimir.k.varbanov@gmail.com, quic_vgarodia@quicinc.com,
agross@kernel.org, andersson@kernel.org, konrad.dybcio@linaro.org,
mchehab@kernel.org, bryan.odonoghue@linaro.org
Cc: linux-arm-msm@vger.kernel.org, quic_abhinavk@quicinc.com,
Dikshita Agarwal <quic_dikshita@quicinc.com>
Subject: [PATCH v2 00/34] Qualcomm video encoder and decoder driver
Date: Mon, 18 Dec 2023 17:01:55 +0530
Message-Id: <1702899149-21321-1-git-send-email-quic_dikshita@quicinc.com>
X-Mailer: git-send-email 2.7.4
X-QCInternal: smtphost
X-QCInternal: smtphost
X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800
signatures=585085
X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800
signatures=585085
X-Proofpoint-ORIG-GUID: UNfyMWvpvxd-6hB5qK3xlslaCbeVU6bf
X-Proofpoint-GUID: UNfyMWvpvxd-6hB5qK3xlslaCbeVU6bf
X-Proofpoint-Virus-Version: vendor=baseguard
engine=ICAP:2.0.272,Aquarius:18.0.997,Hydra:6.0.619,FMLib:17.11.176.26
definitions=2023-12-09_01,2023-12-07_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0
phishscore=0 mlxlogscore=999
impostorscore=0 malwarescore=0 clxscore=1015 mlxscore=0 spamscore=0
suspectscore=0 bulkscore=0 priorityscore=1501 adultscore=0
lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1
engine=8.19.0-2311290000 definitions=main-2312180083
Precedence: bulk
X-Mailing-List: linux-media@vger.kernel.org
List-Id: <linux-media.vger.kernel.org>
List-Subscribe: <mailto:linux-media+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-media+unsubscribe@vger.kernel.org>
X-LSpam-Score: -4.8 (----)
X-LSpam-Report: No,
score=-4.8 required=5.0 tests=BAYES_00=-1.9,DKIM_SIGNED=0.1,DKIM_VALID=-0.1,DKIM_VALID_AU=-0.1,HEADER_FROM_DIFFERENT_DOMAINS=0.5,MAILING_LIST_MULTI=-1,RCVD_IN_DNSWL_MED=-2.3
autolearn=ham autolearn_force=no
|
Message
Dikshita Agarwal
Dec. 18, 2023, 11:31 a.m. UTC
This patch series introduces support for Qualcomm new video acceleration
hardware architecture, used for video stream decoding/encoding. This driver
is based on new communication protocol between video hardware and application
processor.
This driver comes with below capabilities:
- V4L2 complaint video driver with M2M and STREAMING capability.
- Supports H264, H265, VP9 decoders.
- Supports H264, H265 encoders.
This driver comes with below features:
- Centralized resource and memory management.
- Centralized management of core and instance states.
- Defines platform specific capabilities and features. As a results, it provides
a single point of control to enable/disable a given feature depending on
specific platform capabilities.
- Handles hardware interdependent configurations. For a given configuration from
client, the driver checks for hardware dependent configuration/s and updates
the same.
- Handles multiple complex video scenarios involving state transitions - DRC,
Drain, Seek, back to back DRC, DRC during Drain sequence, DRC during Seek
sequence.
- Introduces a flexible way for driver to subscribe for any property with
hardware. Hardware would inform driver with those subscribed property with any
change in value.
- Introduces performance (clock and bus) model based on new hardware
architecture.
- Introduces multi thread safe design to handle communication between client and
hardware.
- Adapts encoder quality improvements available in new hardware architecture.
- Implements asynchronous communication with hardware to achieve better
experience in low latency usecases.
- Supports multi stage hardware architecture for encode/decode.
- Output and capture planes are controlled independently. Thereby providing a
way to reconfigure individual plane.
- Hardware packetization layer supports synchronization between configuration
packet and data packet.
- Introduces a flexibility to receive a hardware response for a given command
packet.
- Native hardware support of LAST flag which is mandatory to align with port
reconfiguration and DRAIN sequence as per V4L guidelines.
- Native hardware support for drain sequence.
Changes done since v1[1]:
- Patches are created as logical split instead of file by file.
- Extracted common functionality between venus and iris driver and placed them
under common folder vcodec.
- Flattened directory structure.
- Restructured the code in a simplified layer architecture.
- Implemented runtime PM, and dropped explicit power collapse thread in driver.
- Moved to standard kernel log print api.
- Simplified the bus and clock calculation logic.
- Removed debug features like dma tracker, frame stats, debugfs.
- Merged v4l2 and vidc layer as vidc in driver.
- Removed separate probe for context bank.
- Use of_device_get_match_data to get platform data.
- Replaced complex macros with inline functions.
- Migrated venus to iris names.
- Addressed many other comments received on [1].
[1]: https://patchwork.kernel.org/project/linux-media/list/?series=770581
Patch 1, adds dt binding for iris driver.
Patches 2-4, are introducing vcodec folder and moving common APIs like fw
load/unload, buffer size calcualtions, read/write to shared queues to common
files which are being used by both venus and iris drivers.
This also moves the venus driver folder to vcodec folder.
Patch 5, adds the maintainers for iris driver.
Patch 6-29, adds core iris driver and enable decoder.
Patch 30-34, enable encoder functionality in iris driver.
Static tools like checkpatch, smatch, dt_binding_check, sparse and Coccinelle
run successfully with this driver.
The output of v4l2-compliance test looks like:
v4l2-compliance SHA: not available, 64 bits
Cannot open device /dev/vido0, exiting.
root@qemuarm64:/usr/bin# ./v4l2-compliance -d /dev/video0
v4l2-compliance SHA: not available, 64 bits
Compliance test for iris_driver device /dev/video0:
Driver Info:
Driver name : iris_driver
Card type : iris_decoder
Bus info : platform:iris_bus
Driver version : 6.6.0
Capabilities : 0x84204000
Video Memory-to-Memory Multiplanar
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x04204000
Video Memory-to-Memory Multiplanar
Streaming
Extended Pix Format
Required ioctls:
test VIDIOC_QUERYCAP: OK
Allow for multiple opens:
test second /dev/video0 open: OK
test VIDIOC_QUERYCAP: OK
test VIDIOC_G/S_PRIORITY: OK
fail: ../../../v4l-utils-1.18.1/utils/v4l2-compliance/v4l2-compliance.cpp(724): !ok
test for unlimited opens: FAIL
Debug ioctls:
test VIDIOC_DBG_G/S_REGISTER: OK (Not Supported)
test VIDIOC_LOG_STATUS: OK (Not Supported)
Input ioctls:
test VIDIOC_G/S_TUNER/ENUM_FREQ_BANDS: OK (Not Supported)
test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
test VIDIOC_S_HW_FREQ_SEEK: OK (Not Supported)
test VIDIOC_ENUMAUDIO: OK (Not Supported)
test VIDIOC_G/S/ENUMINPUT: OK (Not Supported)
test VIDIOC_G/S_AUDIO: OK (Not Supported)
Inputs: 0 Audio Inputs: 0 Tuners: 0
Output ioctls:
test VIDIOC_G/S_MODULATOR: OK (Not Supported)
test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
test VIDIOC_ENUMAUDOUT: OK (Not Supported)
test VIDIOC_G/S/ENUMOUTPUT: OK (Not Supported)
test VIDIOC_G/S_AUDOUT: OK (Not Supported)
Outputs: 0 Audio Outputs: 0 Modulators: 0
Input/Output configuration ioctls:
test VIDIOC_ENUM/G/S/QUERY_STD: OK (Not Supported)
test VIDIOC_ENUM/G/S/QUERY_DV_TIMINGS: OK (Not Supported)
test VIDIOC_DV_TIMINGS_CAP: OK (Not Supported)
test VIDIOC_G/S_EDID: OK (Not Supported)
Control ioctls:
test VIDIOC_QUERY_EXT_CTRL/QUERYMENU: OK
test VIDIOC_QUERYCTRL: OK
test VIDIOC_G/S_CTRL: OK
test VIDIOC_G/S/TRY_EXT_CTRLS: OK
test VIDIOC_(UN)SUBSCRIBE_EVENT/DQEVENT: OK
test VIDIOC_G/S_JPEGCOMP: OK (Not Supported)
Standard Controls: 48 Private Controls: 0
Format ioctls:
test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: OK
test VIDIOC_G/S_PARM: OK (Not Supported)
test VIDIOC_G_FBUF: OK (Not Supported)
test VIDIOC_G_FMT: OK
test VIDIOC_TRY_FMT: OK
test VIDIOC_S_FMT: OK
test VIDIOC_G_SLICED_VBI_CAP: OK (Not Supported)
test Cropping: OK
test Composing: OK
test Scaling: OK
Codec ioctls:
test VIDIOC_(TRY_)ENCODER_CMD: OK (Not Supported)
test VIDIOC_G_ENC_INDEX: OK (Not Supported)
test VIDIOC_(TRY_)DECODER_CMD: OK
Buffer ioctls:
testVIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: OK
test VIDIOC_EXPBUF: OK (Not Supported)
test Requests: OK (Not Supported)
Total for iris_driver device /dev/video0: 44, Succeeded: 43, Failed: 1, Warnings: 0
Compliance test for iris_driver device /dev/video1:
Driver Info:
Driver name : iris_driver
Card type : iris_encoder
Bus info : platform:iris_bus
Driver version : 6.6.0
Capabilities : 0x84204000
Video Memory-to-Memory Multiplanar
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x04204000
Video Memory-to-Memory Multiplanar
Streaming
Extended Pix Format
Required ioctls:
test VIDIOC_QUERYCAP: OK
Allow for multiple opens:
test second /dev/video1 open: OK
test VIDIOC_QUERYCAP: OK
test VIDIOC_G/S_PRIORITY: OK
fail: ../../../v4l-utils-1.18.1/utils/v4l2-compliance/v4l2-compliance.cpp(724): !ok
test for unlimited opens: FAIL
Debug ioctls:
test VIDIOC_DBG_G/S_REGISTER: OK (Not Supported)
test VIDIOC_LOG_STATUS: OK (Not Supported)
Input ioctls:
test VIDIOC_G/S_TUNER/ENUM_FREQ_BANDS: OK (Not Supported)
test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
test VIDIOC_S_HW_FREQ_SEEK: OK (Not Supported)
test VIDIOC_ENUMAUDIO: OK (Not Supported)
test VIDIOC_G/S/ENUMINPUT: OK (Not Supported)
test VIDIOC_G/S_AUDIO: OK (Not Supported)
Inputs: 0 Audio Inputs: 0 Tuners: 0
Output ioctls:
test VIDIOC_G/S_MODULATOR: OK (Not Supported)
test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
test VIDIOC_ENUMAUDOUT: OK (Not Supported)
test VIDIOC_G/S/ENUMOUTPUT: OK (Not Supported)
test VIDIOC_G/S_AUDOUT: OK (Not Supported)
Outputs: 0 Audio Outputs: 0 Modulators: 0
Input/Output configuration ioctls:
test VIDIOC_ENUM/G/S/QUERY_STD: OK (Not Supported)
test VIDIOC_ENUM/G/S/QUERY_DV_TIMINGS: OK (Not Supported)
test VIDIOC_DV_TIMINGS_CAP: OK (Not Supported)
test VIDIOC_G/S_EDID: OK (Not Supported)
Control ioctls:
test VIDIOC_QUERY_EXT_CTRL/QUERYMENU: OK
test VIDIOC_QUERYCTRL: OK
test VIDIOC_G/S_CTRL: OK
test VIDIOC_G/S/TRY_EXT_CTRLS: OK
test VIDIOC_(UN)SUBSCRIBE_EVENT/DQEVENT: OK
test VIDIOC_G/S_JPEGCOMP: OK (Not Supported)
Standard Controls: 48 Private Controls: 0
Format ioctls:
test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: OK
test VIDIOC_G/S_PARM: OK
test VIDIOC_G_FBUF: OK (Not Supported)
test VIDIOC_G_FMT: OK
test VIDIOC_TRY_FMT: OK
test VIDIOC_S_FMT: OK
test VIDIOC_G_SLICED_VBI_CAP: OK (Not Supported)
test Cropping: OK
test Composing: OK
test Scaling: OK (Not Supported)
Codec ioctls:
test VIDIOC_(TRY_)ENCODER_CMD: OK
test VIDIOC_G_ENC_INDEX: OK (Not Supported)
test VIDIOC_(TRY_)DECODER_CMD: OK (Not Supported)
Buffer ioctls:
test VIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: OK
test VIDIOC_EXPBUF: OK (Not Supported)
test Requests: OK (Not Supported)
Total for iris_driver device /dev/video1: 44, Succeeded: 43, Failed: 1, Warnings: 0
Dikshita Agarwal (27):
media: introduce common helpers for video firmware handling
media: introduce common helpers for queues handling
media: introduce common helpers for buffer size calculation
dt-bindings: media: Add sm8550 dt schema
media: MAINTAINERS: Add Qualcomm Iris video accelerator driver
media: iris: register video device to platform driver
media: iris: initialize power resources
media: iris: introduce state machine for iris core
media: iris: initialize shared queues for host and firmware
communication
media: iris: add PIL functionality for video firmware
media: iris: introduce packetization layer for creating HFI packets
media: iris: add video processing unit(VPU) specific register handling
media: iris: introduce platform specific capabilities for core and
instance
media: iris: add handling for interrupt service routine(ISR) invoked
by hardware
media: iris: implement iris v4l2_ctrl_ops and prepare capabilities
media: iris: implement vb2_ops queue setup
media: iris: implement HFI to queue and release buffers
media: iris: add video hardware internal buffer count and size
calculation
media: iris: implement internal buffer management
media: iris: introduce instance states
media: iris: implement vb2 streaming ops on capture and output planes
media: iris: implement vb2 ops for buf_queue and firmware response
media: iris: register video encoder device to platform driver
media: iris: add platform specific instance capabilities for encoder
media: iris: implement iris v4l2 ioctl ops supported by encoder
media: iris: add vb2 streaming and buffer ops for encoder
media: iris: add power management for encoder
Vikash Garodia (7):
media: iris: implement iris v4l2 file ops
media: iris: introduce and implement iris vb2 mem ops
media: iris: implement iris v4l2 ioctl ops supported by decoder
media: iris: subscribe input and output properties to firmware
media: iris: subscribe src change and handle firmware responses
media: iris: add instance sub states and implement DRC and Drain
sequence
media: iris: implement power management
.../bindings/media/qcom,sm8550-iris.yaml | 177 ++
MAINTAINERS | 11 +
drivers/media/platform/qcom/Kconfig | 3 +-
drivers/media/platform/qcom/Makefile | 3 +-
drivers/media/platform/qcom/vcodec/buffers.c | 103 ++
drivers/media/platform/qcom/vcodec/buffers.h | 15 +
drivers/media/platform/qcom/vcodec/firmware.c | 147 ++
drivers/media/platform/qcom/vcodec/firmware.h | 21 +
drivers/media/platform/qcom/vcodec/hfi_queue.c | 258 +++
drivers/media/platform/qcom/vcodec/hfi_queue.h | 129 ++
drivers/media/platform/qcom/vcodec/iris/Kconfig | 13 +
drivers/media/platform/qcom/vcodec/iris/Makefile | 26 +
.../media/platform/qcom/vcodec/iris/hfi_defines.h | 386 +++++
.../media/platform/qcom/vcodec/iris/iris_buffer.c | 833 +++++++++
.../media/platform/qcom/vcodec/iris/iris_buffer.h | 65 +
.../media/platform/qcom/vcodec/iris/iris_common.h | 147 ++
.../media/platform/qcom/vcodec/iris/iris_core.c | 110 ++
.../media/platform/qcom/vcodec/iris/iris_core.h | 121 ++
.../media/platform/qcom/vcodec/iris/iris_ctrls.c | 1782 ++++++++++++++++++++
.../media/platform/qcom/vcodec/iris/iris_ctrls.h | 71 +
.../media/platform/qcom/vcodec/iris/iris_helpers.c | 1099 ++++++++++++
.../media/platform/qcom/vcodec/iris/iris_helpers.h | 68 +
drivers/media/platform/qcom/vcodec/iris/iris_hfi.c | 917 ++++++++++
drivers/media/platform/qcom/vcodec/iris/iris_hfi.h | 47 +
.../platform/qcom/vcodec/iris/iris_hfi_packet.c | 729 ++++++++
.../platform/qcom/vcodec/iris/iris_hfi_packet.h | 118 ++
.../platform/qcom/vcodec/iris/iris_hfi_response.c | 1097 ++++++++++++
.../platform/qcom/vcodec/iris/iris_hfi_response.h | 20 +
.../platform/qcom/vcodec/iris/iris_instance.h | 106 ++
.../media/platform/qcom/vcodec/iris/iris_power.c | 178 ++
.../media/platform/qcom/vcodec/iris/iris_power.h | 15 +
.../media/platform/qcom/vcodec/iris/iris_probe.c | 357 ++++
.../media/platform/qcom/vcodec/iris/iris_state.c | 453 +++++
.../media/platform/qcom/vcodec/iris/iris_state.h | 78 +
drivers/media/platform/qcom/vcodec/iris/iris_vb2.c | 457 +++++
drivers/media/platform/qcom/vcodec/iris/iris_vb2.h | 28 +
.../media/platform/qcom/vcodec/iris/iris_vdec.c | 1211 +++++++++++++
.../media/platform/qcom/vcodec/iris/iris_vdec.h | 25 +
.../media/platform/qcom/vcodec/iris/iris_venc.c | 948 +++++++++++
.../media/platform/qcom/vcodec/iris/iris_venc.h | 27 +
.../media/platform/qcom/vcodec/iris/iris_vidc.c | 1419 ++++++++++++++++
.../media/platform/qcom/vcodec/iris/iris_vidc.h | 15 +
.../platform/qcom/vcodec/iris/platform_common.c | 29 +
.../platform/qcom/vcodec/iris/platform_common.h | 323 ++++
.../platform/qcom/vcodec/iris/platform_sm8550.c | 1190 +++++++++++++
.../media/platform/qcom/vcodec/iris/resources.c | 506 ++++++
.../media/platform/qcom/vcodec/iris/resources.h | 44 +
.../media/platform/qcom/vcodec/iris/vpu_common.c | 158 ++
.../media/platform/qcom/vcodec/iris/vpu_common.h | 52 +
.../media/platform/qcom/vcodec/iris/vpu_iris3.c | 568 +++++++
.../media/platform/qcom/vcodec/iris/vpu_iris3.h | 13 +
.../platform/qcom/vcodec/iris/vpu_iris3_buffer.c | 395 +++++
.../platform/qcom/vcodec/iris/vpu_iris3_buffer.h | 1469 ++++++++++++++++
.../platform/qcom/vcodec/iris/vpu_iris3_power.c | 148 ++
.../platform/qcom/vcodec/iris/vpu_iris3_power.h | 13 +
.../media/platform/qcom/{ => vcodec}/venus/Kconfig | 0
.../platform/qcom/{ => vcodec}/venus/Makefile | 5 +-
.../media/platform/qcom/{ => vcodec}/venus/core.c | 102 +-
.../media/platform/qcom/{ => vcodec}/venus/core.h | 0
.../media/platform/qcom/{ => vcodec}/venus/dbgfs.c | 0
.../media/platform/qcom/{ => vcodec}/venus/dbgfs.h | 0
.../platform/qcom/vcodec/venus/firmware_no_tz.c | 194 +++
.../platform/qcom/vcodec/venus/firmware_no_tz.h | 19 +
.../platform/qcom/{ => vcodec}/venus/helpers.c | 172 +-
.../platform/qcom/{ => vcodec}/venus/helpers.h | 2 +-
.../media/platform/qcom/{ => vcodec}/venus/hfi.c | 0
.../media/platform/qcom/{ => vcodec}/venus/hfi.h | 0
.../platform/qcom/{ => vcodec}/venus/hfi_cmds.c | 0
.../platform/qcom/{ => vcodec}/venus/hfi_cmds.h | 0
.../platform/qcom/{ => vcodec}/venus/hfi_helper.h | 0
.../platform/qcom/{ => vcodec}/venus/hfi_msgs.c | 0
.../platform/qcom/{ => vcodec}/venus/hfi_msgs.h | 0
.../platform/qcom/{ => vcodec}/venus/hfi_parser.c | 0
.../platform/qcom/{ => vcodec}/venus/hfi_parser.h | 0
.../qcom/{ => vcodec}/venus/hfi_plat_bufs.h | 4 +-
.../qcom/{ => vcodec}/venus/hfi_plat_bufs_v6.c | 10 +-
.../qcom/{ => vcodec}/venus/hfi_platform.c | 0
.../qcom/{ => vcodec}/venus/hfi_platform.h | 0
.../qcom/{ => vcodec}/venus/hfi_platform_v4.c | 0
.../qcom/{ => vcodec}/venus/hfi_platform_v6.c | 0
.../platform/qcom/{ => vcodec}/venus/hfi_venus.c | 521 +-----
.../platform/qcom/{ => vcodec}/venus/hfi_venus.h | 0
.../qcom/{ => vcodec}/venus/hfi_venus_io.h | 0
.../platform/qcom/{ => vcodec}/venus/pm_helpers.c | 0
.../platform/qcom/{ => vcodec}/venus/pm_helpers.h | 0
.../media/platform/qcom/{ => vcodec}/venus/vdec.c | 5 +-
.../media/platform/qcom/{ => vcodec}/venus/vdec.h | 0
.../platform/qcom/{ => vcodec}/venus/vdec_ctrls.c | 0
.../media/platform/qcom/{ => vcodec}/venus/venc.c | 0
.../media/platform/qcom/{ => vcodec}/venus/venc.h | 0
.../platform/qcom/{ => vcodec}/venus/venc_ctrls.c | 0
drivers/media/platform/qcom/venus/firmware.c | 363 ----
drivers/media/platform/qcom/venus/firmware.h | 26 -
93 files changed, 19175 insertions(+), 989 deletions(-)
create mode 100644 Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml
create mode 100644 drivers/media/platform/qcom/vcodec/buffers.c
create mode 100644 drivers/media/platform/qcom/vcodec/buffers.h
create mode 100644 drivers/media/platform/qcom/vcodec/firmware.c
create mode 100644 drivers/media/platform/qcom/vcodec/firmware.h
create mode 100644 drivers/media/platform/qcom/vcodec/hfi_queue.c
create mode 100644 drivers/media/platform/qcom/vcodec/hfi_queue.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/Kconfig
create mode 100644 drivers/media/platform/qcom/vcodec/iris/Makefile
create mode 100644 drivers/media/platform/qcom/vcodec/iris/hfi_defines.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_buffer.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_buffer.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_common.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_core.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_core.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_ctrls.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_ctrls.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_helpers.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_helpers.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_hfi.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_hfi.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_hfi_packet.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_hfi_packet.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_hfi_response.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_hfi_response.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_instance.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_power.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_power.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_probe.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_state.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_state.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_vb2.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_vb2.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_vdec.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_vdec.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_venc.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_venc.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_vidc.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/iris_vidc.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/platform_common.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/platform_common.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/platform_sm8550.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/resources.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/resources.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/vpu_common.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/vpu_common.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/vpu_iris3.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/vpu_iris3.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/vpu_iris3_buffer.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/vpu_iris3_buffer.h
create mode 100644 drivers/media/platform/qcom/vcodec/iris/vpu_iris3_power.c
create mode 100644 drivers/media/platform/qcom/vcodec/iris/vpu_iris3_power.h
rename drivers/media/platform/qcom/{ => vcodec}/venus/Kconfig (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/Makefile (75%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/core.c (91%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/core.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/dbgfs.c (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/dbgfs.h (100%)
create mode 100644 drivers/media/platform/qcom/vcodec/venus/firmware_no_tz.c
create mode 100644 drivers/media/platform/qcom/vcodec/venus/firmware_no_tz.h
rename drivers/media/platform/qcom/{ => vcodec}/venus/helpers.c (90%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/helpers.h (98%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi.c (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_cmds.c (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_cmds.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_helper.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_msgs.c (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_msgs.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_parser.c (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_parser.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_plat_bufs.h (94%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_plat_bufs_v6.c (99%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_platform.c (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_platform.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_platform_v4.c (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_platform_v6.c (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_venus.c (73%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_venus.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/hfi_venus_io.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/pm_helpers.c (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/pm_helpers.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/vdec.c (99%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/vdec.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/vdec_ctrls.c (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/venc.c (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/venc.h (100%)
rename drivers/media/platform/qcom/{ => vcodec}/venus/venc_ctrls.c (100%)
delete mode 100644 drivers/media/platform/qcom/venus/firmware.c
delete mode 100644 drivers/media/platform/qcom/venus/firmware.h
Comments
Hello All, On 12/18/2023 5:01 PM, Dikshita Agarwal wrote: > This patch series introduces support for Qualcomm new video acceleration > hardware architecture, used for video stream decoding/encoding. This driver > is based on new communication protocol between video hardware and application > processor. > This driver comes with below capabilities: > - V4L2 complaint video driver with M2M and STREAMING capability. > - Supports H264, H265, VP9 decoders. > - Supports H264, H265 encoders. > This driver comes with below features: > - Centralized resource and memory management. > - Centralized management of core and instance states. > - Defines platform specific capabilities and features. As a results, it provides > a single point of control to enable/disable a given feature depending on > specific platform capabilities. > - Handles hardware interdependent configurations. For a given configuration from > client, the driver checks for hardware dependent configuration/s and updates > the same. > - Handles multiple complex video scenarios involving state transitions - DRC, > Drain, Seek, back to back DRC, DRC during Drain sequence, DRC during Seek > sequence. > - Introduces a flexible way for driver to subscribe for any property with > hardware. Hardware would inform driver with those subscribed property with any > change in value. > - Introduces performance (clock and bus) model based on new hardware > architecture. > - Introduces multi thread safe design to handle communication between client and > hardware. > - Adapts encoder quality improvements available in new hardware architecture. > - Implements asynchronous communication with hardware to achieve better > experience in low latency usecases. > - Supports multi stage hardware architecture for encode/decode. > - Output and capture planes are controlled independently. Thereby providing a > way to reconfigure individual plane. > - Hardware packetization layer supports synchronization between configuration > packet and data packet. > - Introduces a flexibility to receive a hardware response for a given command > packet. > - Native hardware support of LAST flag which is mandatory to align with port > reconfiguration and DRAIN sequence as per V4L guidelines. > - Native hardware support for drain sequence. 1. We considered enhancing the venus driver to support iris functionality but concluded that the result would essentially be two parallel drivers implemented in the same folder. 2. Although the underlying hardware for venus and iris are quite similar, but there are other factors which brings the need of new driver: a. the host firmware interface (HFI) changed between the two. Venus supports HFI protocol 1.0 while iris supports HFI protocol 2.0. b. unlike HFI protocol 1.0, HFI protocol 2.0 is better aligned to V4L2 APIs. c. iris driver modularize platforms, hardware variants, and states to extend it for any upcoming SOC. Thereby more extendable to newer SOCs in future. d. Iris also supports many advanced features. 3. Based on the comments received on posted iris driver [1], we evaluated it further and to better align with the upstream standard and practices, we acknowledge that even though iris driver is the way forward, it would be ideal to bring in the Venus hardwares enabled in this driver. 4. Hence, we decided to rework iris driver to add support of HFI protocol 1.0 as well. 5. Initially we would start with adding support for one HFI protocol 1.0 based platform which would be SM8250. 6. SM8250 enablement on iris driver would be incremental, starting with basic decode for H264 codec. 7. In long-term, all venus supported platforms would be migrated to iris. 8. Iris driver and venus driver will co-exist till remaining supported targets also gets migrated to iris driver. 9. We would continue to support and maintain venus driver during this phased out approach. Please share your thoughts on the above proposal. [1] https://patchwork.kernel.org/project/linux-media/cover/1702899149-21321-1-git-send-email-quic_dikshita@quicinc.com/#25643473 Regards, Vikash
Hi Vikash, On 2/29/24 16:09, Vikash Garodia wrote: > Hello All, > > On 12/18/2023 5:01 PM, Dikshita Agarwal wrote: >> This patch series introduces support for Qualcomm new video acceleration >> hardware architecture, used for video stream decoding/encoding. This driver >> is based on new communication protocol between video hardware and application >> processor. >> This driver comes with below capabilities: >> - V4L2 complaint video driver with M2M and STREAMING capability. >> - Supports H264, H265, VP9 decoders. >> - Supports H264, H265 encoders. >> This driver comes with below features: >> - Centralized resource and memory management. >> - Centralized management of core and instance states. >> - Defines platform specific capabilities and features. As a results, it provides >> a single point of control to enable/disable a given feature depending on >> specific platform capabilities. >> - Handles hardware interdependent configurations. For a given configuration from >> client, the driver checks for hardware dependent configuration/s and updates >> the same. >> - Handles multiple complex video scenarios involving state transitions - DRC, >> Drain, Seek, back to back DRC, DRC during Drain sequence, DRC during Seek >> sequence. >> - Introduces a flexible way for driver to subscribe for any property with >> hardware. Hardware would inform driver with those subscribed property with any >> change in value. >> - Introduces performance (clock and bus) model based on new hardware >> architecture. >> - Introduces multi thread safe design to handle communication between client and >> hardware. >> - Adapts encoder quality improvements available in new hardware architecture. >> - Implements asynchronous communication with hardware to achieve better >> experience in low latency usecases. >> - Supports multi stage hardware architecture for encode/decode. >> - Output and capture planes are controlled independently. Thereby providing a >> way to reconfigure individual plane. >> - Hardware packetization layer supports synchronization between configuration >> packet and data packet. >> - Introduces a flexibility to receive a hardware response for a given command >> packet. >> - Native hardware support of LAST flag which is mandatory to align with port >> reconfiguration and DRAIN sequence as per V4L guidelines. >> - Native hardware support for drain sequence. > > 1. We considered enhancing the venus driver to support iris functionality but > concluded that the result would essentially be two parallel drivers implemented > in the same folder. > 2. Although the underlying hardware for venus and iris are quite similar, but > there are other factors which brings the need of new driver: > a. the host firmware interface (HFI) changed between the two. Venus supports > HFI protocol 1.0 while iris supports HFI protocol 2.0. > b. unlike HFI protocol 1.0, HFI protocol 2.0 is better aligned to V4L2 APIs. > c. iris driver modularize platforms, hardware variants, and states to extend > it for any upcoming SOC. Thereby more extendable to newer SOCs in future. > d. Iris also supports many advanced features. > 3. Based on the comments received on posted iris driver [1], we evaluated it > further and to better align with the upstream standard and practices, we > acknowledge that even though iris driver is the way forward, it would be ideal > to bring in the Venus hardwares enabled in this driver. > 4. Hence, we decided to rework iris driver to add support of HFI protocol 1.0 as > well. > 5. Initially we would start with adding support for one HFI protocol 1.0 based > platform which would be SM8250. > 6. SM8250 enablement on iris driver would be incremental, starting with basic > decode for H264 codec. > 7. In long-term, all venus supported platforms would be migrated to iris. > 8. Iris driver and venus driver will co-exist till remaining supported targets > also gets migrated to iris driver. > 9. We would continue to support and maintain venus driver during this phased out > approach. > > Please share your thoughts on the above proposal. I think this is a reasonable approach: the venus driver is quite old and it was created when we were at more-or-less the same time also developing better codec frameworks. So it is not quite up-to-date with all the latest requirements. Starting with a clean slate for the iris driver and then add support for venus platforms to the iris driver makes sense. Just one serious concern: who will do the venus platform migration? Are there resources available to do that work? Or is this just wishful thinking? Regards, Hans > > [1] > https://patchwork.kernel.org/project/linux-media/cover/1702899149-21321-1-git-send-email-quic_dikshita@quicinc.com/#25643473 > > Regards, > Vikash >
Hi Hans, On 3/12/2024 4:07 PM, Hans Verkuil wrote: > Hi Vikash, > > On 2/29/24 16:09, Vikash Garodia wrote: >> Hello All, >> >> On 12/18/2023 5:01 PM, Dikshita Agarwal wrote: >>> This patch series introduces support for Qualcomm new video acceleration >>> hardware architecture, used for video stream decoding/encoding. This driver >>> is based on new communication protocol between video hardware and application >>> processor. >>> This driver comes with below capabilities: >>> - V4L2 complaint video driver with M2M and STREAMING capability. >>> - Supports H264, H265, VP9 decoders. >>> - Supports H264, H265 encoders. >>> This driver comes with below features: >>> - Centralized resource and memory management. >>> - Centralized management of core and instance states. >>> - Defines platform specific capabilities and features. As a results, it provides >>> a single point of control to enable/disable a given feature depending on >>> specific platform capabilities. >>> - Handles hardware interdependent configurations. For a given configuration from >>> client, the driver checks for hardware dependent configuration/s and updates >>> the same. >>> - Handles multiple complex video scenarios involving state transitions - DRC, >>> Drain, Seek, back to back DRC, DRC during Drain sequence, DRC during Seek >>> sequence. >>> - Introduces a flexible way for driver to subscribe for any property with >>> hardware. Hardware would inform driver with those subscribed property with any >>> change in value. >>> - Introduces performance (clock and bus) model based on new hardware >>> architecture. >>> - Introduces multi thread safe design to handle communication between client and >>> hardware. >>> - Adapts encoder quality improvements available in new hardware architecture. >>> - Implements asynchronous communication with hardware to achieve better >>> experience in low latency usecases. >>> - Supports multi stage hardware architecture for encode/decode. >>> - Output and capture planes are controlled independently. Thereby providing a >>> way to reconfigure individual plane. >>> - Hardware packetization layer supports synchronization between configuration >>> packet and data packet. >>> - Introduces a flexibility to receive a hardware response for a given command >>> packet. >>> - Native hardware support of LAST flag which is mandatory to align with port >>> reconfiguration and DRAIN sequence as per V4L guidelines. >>> - Native hardware support for drain sequence. >> >> 1. We considered enhancing the venus driver to support iris functionality but >> concluded that the result would essentially be two parallel drivers implemented >> in the same folder. >> 2. Although the underlying hardware for venus and iris are quite similar, but >> there are other factors which brings the need of new driver: >> a. the host firmware interface (HFI) changed between the two. Venus supports >> HFI protocol 1.0 while iris supports HFI protocol 2.0. >> b. unlike HFI protocol 1.0, HFI protocol 2.0 is better aligned to V4L2 APIs. >> c. iris driver modularize platforms, hardware variants, and states to extend >> it for any upcoming SOC. Thereby more extendable to newer SOCs in future. >> d. Iris also supports many advanced features. >> 3. Based on the comments received on posted iris driver [1], we evaluated it >> further and to better align with the upstream standard and practices, we >> acknowledge that even though iris driver is the way forward, it would be ideal >> to bring in the Venus hardwares enabled in this driver. >> 4. Hence, we decided to rework iris driver to add support of HFI protocol 1.0 as >> well. >> 5. Initially we would start with adding support for one HFI protocol 1.0 based >> platform which would be SM8250. >> 6. SM8250 enablement on iris driver would be incremental, starting with basic >> decode for H264 codec. >> 7. In long-term, all venus supported platforms would be migrated to iris. >> 8. Iris driver and venus driver will co-exist till remaining supported targets >> also gets migrated to iris driver. >> 9. We would continue to support and maintain venus driver during this phased out >> approach. >> >> Please share your thoughts on the above proposal. > > I think this is a reasonable approach: the venus driver is quite old and it was > created when we were at more-or-less the same time also developing better codec > frameworks. So it is not quite up-to-date with all the latest requirements. > > Starting with a clean slate for the iris driver and then add support for venus > platforms to the iris driver makes sense. Appreciate your time to review the proposal. > > Just one serious concern: who will do the venus platform migration? Are there resources > available to do that work? Or is this just wishful thinking? To initiate the venus platform migration, iris driver would be enabled with all SOCs under HFI_V6XX which are currently supported in venus driver. In doing so, iris driver, posted earlier [1] is being reworked to have cleaner abstraction to invoke HFI 1.0 protocol (venus variants) and would be applicable for all venus platforms. With this, remaining platform migration would be done with some incremental efforts (platform specific handling). We would like to get help from community and co-work in enabling the migration for remaining venus platforms in a phased out approach. Regards, Vikash [1] https://patchwork.kernel.org/project/linux-media/cover/1702899149-21321-1-git-send-email-quic_dikshita@quicinc.com/#25643473
Hi, I'm trying this series of patches for enabling /dev/video0 on sm8650 hdk but failed. After modprobing, lsmod says just like the follwoing: root@hdk8650:/lib/modules/6.7.0-rc3+# lsmod Module Size Used by iris 110592 -2 v4l2_mem2mem 20480 -2 videobuf2_memops 12288 -2 videobuf2_v4l2 20480 -2 videobuf2_common 45056 -2 videodev 176128 -2 This series looks for sm8550 device though, my question is that this series have been tested on the device (sm8650 hdk)? or do you expect this should work on it?
On 12/04/2024 08:13, Hyunjun Ko wrote: > Hi, > > I'm trying this series of patches for enabling /dev/video0 on sm8650 hdk but failed. > After modprobing, lsmod says just like the follwoing: > > root@hdk8650:/lib/modules/6.7.0-rc3+# lsmod > Module Size Used by > iris 110592 -2 > v4l2_mem2mem 20480 -2 > videobuf2_memops 12288 -2 > videobuf2_v4l2 20480 -2 > videobuf2_common 45056 -2 > videodev 176128 -2 > > > This series looks for sm8550 device though, my question is that this series have been tested on the device (sm8650 hdk)? or do you expect this should work on it? > Different SoCs so despite how close they look in version numbers, you'd expect at a minimum some clock and/or power-domain churn - even if there is a 1:1 mapping in register numbers and offsets. We wouldn't ordinarily expect to be able to be able to move SoC versions so easily - 8550 and 8650 have similar SoC version numbers but, this is not necessarily an indicator of silicon IP block version reuse. --- bod
Hi, Thanks for this series of patches. I successfully adjusted these patches and tried to test video features with gstreamer or ffmpeg. But I found this provides staetful interfaces while I need stateless, which might cause an issue for my side.. My question is do you have any plan to implement stateless interfaces or already you have somewhere?
Hi, On 5/16/2024 1:27 PM, Hyunjun Ko wrote: > Hi, > > Thanks for this series of patches. I successfully adjusted these patches and tried to test video features with gstreamer or ffmpeg. > But I found this provides staetful interfaces while I need stateless, which might cause an issue for my side.. > > My question is do you have any plan to implement stateless interfaces or already you have somewhere? There is no plan to implement stateless interfaces. Regards, Vikash