linux-kernel - Proposal for a new video driver for Qualcomm upcoming SOCs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <90e7d1402f1f4ad3e43b7d1f8746aef0@codeaurora.org>
Date:   Mon, 28 Mar 2022 22:42:42 +0530
From:   vgarodia@...eaurora.org
To:     mchehab@...nel.org, hverkuil@...all.nl,
        stanimir.varbanov@...aro.org
Cc:     linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
        quic_vgarodia@...cinc.com
Subject: Proposal for a new video driver for Qualcomm upcoming SOCs

Hi All,

There is an existing video driver for Qualcomm SOCs [1]. There is a need 
for a separate driver for the new generations of video hardware in 
Qualcomm SOCs. It is needed, primarily for below reasons:-

1. HFI 2.0 interface (driver<->firmware interface) is a new non-backward 
compatible interface.
    a. HFI 2.0 is designed to suit future video hardware generations.
    b. Older interface (HFI 1.0) is supported till MSM8350 (SD 835). Any 
new video hardware would be supported *only* with the
       new HFI 2.0.

2. Video firmwares, which are based on HFI 1.0, were designed to follow 
khronos openmax IL 1.1.2 specification. Video firmware
    interface HFI 2.0 is designed based on v4l2 stateful codec 
specification.

This request is to share your suggestions or any queries to discuss on 
this proposal.
Incase any aspect to consider, before we start implementing the new 
driver.

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/media/platform/qcom/venus

Regards,
Vikash