linux-kernel - Re: [PATCH v3 0/5] Introduce "non-pixel" sub node within iris video node

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <98e6acf8-80d7-4894-b4ce-ce74660722ef@kernel.org>
Date: Thu, 9 Oct 2025 01:55:22 +0100
From: Bryan O'Donoghue <bod@...nel.org>
To: Krzysztof Kozlowski <krzk@...nel.org>,
 Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
 Charan Teja Kalla <charan.kalla@....qualcomm.com>,
 Bryan O'Donoghue <bod.linux@...w.ie>,
 Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
 Vikash Garodia <quic_vgarodia@...cinc.com>,
 Dikshita Agarwal <quic_dikshita@...cinc.com>,
 Abhinav Kumar <abhinav.kumar@...ux.dev>,
 Mauro Carvalho Chehab <mchehab@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, linux-media@...r.kernel.org,
 linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/5] Introduce "non-pixel" sub node within iris video
 node

On 09/10/2025 01:47, Krzysztof Kozlowski wrote:
>> Maybe it would be possible to also use an inferred FUNCTION_ID somehow
>> though TBH I think that's a work-around.
> Three months ago I gave you the answer for that - it is inferred by
> index on the list.

But at least as I understand it, you can have multiple SID entries that 
need to map to a FUNCTION_ID which means you need to encode that 
inferred indexing in your driver.

So you can't have the iommu code just know what to do.. it has to be 
driver specific.

The iommu description for this platform basically lacks the data that 
_should_ be there -> FUNCTION_ID.

The rule is that the DT should really describe the hardware right ?

---
bod