• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 376 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VH-Q1: v4l2-compliance test failed

haijun
Intellectual 575 points

Part Number: TDA4VH-Q1

Hello,

I am working with j784s4-evm with sdk0900, when I run the command: `v4l2-compliance -s` , the dmesg shows some errors in wave5 driver. I would like to know why this happen and would the v4l2 driver function well on this platform?

j784s4-evm-dmesg.txt

  • 0
    TI__Expert 3840 points

    Hello,

    The driver that is included in the 9.0 SDK is v4l2 compliant in that all of the functions are implemented and will pass the simple compliance test. However, as you have seen in the test, there were still some streaming bugs leading it to not be accepted upstream. A reworked version of the driver (https://lore.kernel.org/lkml/20230929-wave5_v13_media_master-v13-0-5ac60ccbf2ce@collabora.com/) is very close to being accepted and will not have the issues that you see in this compliance test.

    Aside from this, the v4l2 driver is functional and works well on this platform. It is constantly being update and tested based on many different use cases. If there is a bug in a stream that you are working with, please report it on e2e and a patch will be sent. As I said, there are some corner cases that fail in this version of the driver. Once the driver is accepted upstream, it will be backported to our LTS tree.

    Best,

    Brandon

  • 0 in reply to Brandon Brnich
    Intellectual 575 points

    Thanks, we will try this patch later.

  • 0 in reply to haijun
    TI__Expert 3840 points

    Just want to make it clear that the link I shared is the upstream version of the driver, which is built and tested again upstream kernel. The kernel that is a part of our SDK is not the upstream one. 

    Once the upstream version is accepted against upstream kernel, it will be backported into our SDK, as I mentioned above.

    Thank,

    Brandon