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>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f5df1c29-a1cd-4cc7-8ac4-b4aefc4225b0@kernel.org>
Date: Thu, 16 Oct 2025 11:54:20 +0100
From: Bryan O'Donoghue <bod@...nel.org>
To: Hangxiang Ma <hangxiang.ma@....qualcomm.com>,
 Loic Poulain <loic.poulain@....qualcomm.com>, Robert Foss
 <rfoss@...nel.org>, Andi Shyti <andi.shyti@...nel.org>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Todor Tomov <todor.too@...il.com>,
 Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>,
 Mauro Carvalho Chehab <mchehab@...nel.org>
Cc: linux-i2c@...r.kernel.org, linux-arm-msm@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-media@...r.kernel.org, aiqun.yu@....qualcomm.com,
 tingwei.zhang@....qualcomm.com, trilok.soni@....qualcomm.com,
 yijie.yang@....qualcomm.com, Jingyi Wang <jingyi.wang@....qualcomm.com>,
 Atiya Kailany <atiya.kailany@....qualcomm.com>
Subject: Re: [PATCH v2 6/6] media: qcom: camss: vfe: Add support for VFE 1080

On 16/10/2025 11:33, Hangxiang Ma wrote:
>> But why ?
>>
>> ---
>> bod
> That a story. When testing the RDI path on Kaanapali, we found one image
> buffer starved at 19/20 stage. We want to capture 20 images but only 19
> received.
> 
> On Kaanapali, the AUP and RUP are split into two separate registers not
> a single one. Maybe this hardware change impacts something. Calling
> ops->reg_update() in vfe_enable_output_v2 function only applies one
> buffer address. The downstream code defers AUP and RUP to CSID
> configuration stage. We mimic that and find it can solve this issue.
> 
> ---
> Hangxiang

So this is the type of interesting detail that I'd go looking for in a 
commit log, a comment in the code or a footnote in the cover letter.

One or two sentences in the commit log will do.

---
bod

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ