[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e954a3b7-296f-4dbf-8325-b5993d11da92@kernel.org>
Date: Mon, 14 Oct 2024 13:54:46 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Dikshita Agarwal <quic_dikshita@...cinc.com>,
Vikash Garodia <quic_vgarodia@...cinc.com>,
Abhinav Kumar <quic_abhinavk@...cinc.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Philipp Zabel <p.zabel@...gutronix.de>
Cc: Hans Verkuil <hverkuil@...all.nl>,
Sebastian Fricke <sebastian.fricke@...labora.com>,
linux-arm-msm@...r.kernel.org, linux-media@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Vedang Nagar <quic_vnagar@...cinc.com>
Subject: Re: [PATCH v4 00/28] Qualcomm iris video decoder driver
On 14/10/2024 11:07, Dikshita Agarwal wrote:
> Introduce support for Qualcomm new video acceleration hardware i.e.
> iris, used for video stream decoding.
>
> Iris is a multi pipe based hardware that offloads video stream decoding
> from the application processor (AP). It supports H.264 decoding.
> The AP communicates with hardware through a well defined protocol,
> called as host firmware interface (HFI), which provides fine-grained
> and asynchronous control over individual hardware features.
>
> This driver implements upgraded HFI gen2 to communicate with firmware.
> It supports SM8550 which is based out of HFI gen 2. It also supports
> SM8250 which is based out of HFI gen1.
>
> This driver comes with below capabilities:
> - V4L2 complaint video driver with M2M and STREAMING capability.
> - Supports H264 decoder.
>
> This driver comes with below features:
> - Centralized resource 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 various video recommended sequences, like DRC, Drain, Seek,
> EOS.
> - Implements asynchronous communication with hardware to achieve better
> experience in low latency usecases.
> - Output and capture planes are controlled independently. Thereby
> providing a way to reconfigure individual plane.
> - Native hardware support of LAST flag which is mandatory to align with
> port reconfiguration and DRAIN sequence as per V4L guidelines.
>
> Changes since v3:
You send the patches with b4, so why do you strip the link to previous
series? It makes out life just more difficult. Include the link, how the
b4 instructs you.
Best regards,
Krzysztof
Powered by blists - more mailing lists