On 18/12/2023 11:31, Dikshita Agarwal wrote:
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
Good to see some code sharing, is there no way to facilitate the new
code in existing venus ?
I applied your patches to -stable and was happy to find they didn't
break venus on rb5, at least for the superficial test I did [1]. The
names you export here look odd though.
"Driver name" and "Cart Type" should be something like "qcom-iris" and
"Qualcomm Iris video decoder"
v4l2-compliance -d /dev/video15
v4l2-compliance 1.24.1, 64 bits, 64-bit time_t
Compliance test for qcom-venus device /dev/video15:
Driver Info:
Driver name : qcom-venus
Card type : Qualcomm Venus video encoder
Bus info : platform:qcom-venus
Driver version : 6.7.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
Detected Stateful Encoder
[1]
https://file-examples.com/index.php/sample-video-files/sample-mp4-files/
ffplay -loglevel debug -codec:video h264_v4l2m2m -i sample-30s.mp4
Driver Info:
Driver name : iris_driver
Card type : iris_encoder
Same comment on normalising names wrt to venus.
---
bod
