linux-kernel - Re: [PATCH v6 1/5] media: dt-bindings: Add CAMSS device for Kaanapali

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: <2ce4e296-701a-4354-8988-87525769ccac@linaro.org>
Date: Wed, 17 Dec 2025 03:29:00 +0000
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Vijay Kumar Tumati <vijay.tumati@....qualcomm.com>,
 Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>,
 Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
 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>,
 Mauro Carvalho Chehab <mchehab@...nel.org>
Cc: 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 v6 1/5] media: dt-bindings: Add CAMSS device for Kaanapali

On 17/12/2025 00:46, Vijay Kumar Tumati wrote:
>> I don't understand a reason why to do worse for the upstream, when 
>> there is
>> a clear and feasible alternative not to do worse, thus my 
>> misunderstanding
>> and my grief for upstream CAMSS are my concerns.
>>
> Thanks for the comments, Vladimir. Bryan's and Krzysztof's argument was 
> that the bindings are required to describe the full hardware regardless 
> of the driver support and either way not modifiable in the future, so 
> they preferred having the HW properties of the key functional blocks in 
> the bindings. And we were specifically asked to add the properties into 
> this node in this patch series. Having said that, my knowledge on how 
> the bindings are handled upstream in the long run as the requirements 
> evolve, is limited. So I will look for some expert advise from Bryan 
> here as he strongly advised for these. Thanks again.

I see no technical reason why describing the whole hardware block 
precludes any further work. How could it ?

Anyway, I'll repeat my ask to describe:

- The full register set
- The interconnects
- The clocks and resets
- The SIDs

---
bod