Re: [PATCH v2 6/7] media: iris: add iris4 specific H265 line buffer calculation
From: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
Date: 2026-03-04 15:40:43
Also in:
linux-arm-msm, linux-iommu, linux-media, lkml
On 3/4/2026 3:58 AM, Dmitry Baryshkov wrote:
On Wed, Mar 04, 2026 at 12:18:58AM +0530, Vikash Garodia wrote:quoted
On 2/28/2026 1:58 AM, Dmitry Baryshkov wrote:quoted
On Fri, Feb 27, 2026 at 07:41:22PM +0530, Vikash Garodia wrote:quoted
The H265 decoder line buffer size calculation for iris4 (VPU4) was previously reusing the iris3 formula. While this works for most resolutions, certain configurations require a larger buffer size on iris4, causing firmware errors during decode. This resolves firmware failures seen with specific test vectors on kaanapali (iris4), and fixes the following failing fluster tests - PICSIZE_C_Bossen_1 - WPP_E_ericsson_MAIN_2This reminds me of the commit fixing SC7280 support. Should SC7280 or all VPU2.0 platforms also use separate formula?for vpu2, there is already a separate formulaIt was more of "do we need separate formulas within vpu2".
vpu2/3 uses the same one currently here [1]. vpu4 seems to be using quite a different formula to consider it within vpu2/3. [1]https://elixir.bootlin.com/linux/v6.19.3/source/drivers/media/platform/qcom/iris/iris_vpu_buffer.c#L313
quoted
quoted
quoted
Co-developed-by: Vishnu Reddy <redacted> Signed-off-by: Vishnu Reddy <redacted> Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com> --- drivers/media/platform/qcom/iris/iris_vpu_buffer.c | 51 +++++++++++++++++++++- 1 file changed, 50 insertions(+), 1 deletion(-)