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: <3166b396-7aa8-47d7-8d44-e7d88f920c15@oss.qualcomm.com>
Date: Thu, 9 Oct 2025 14:36:56 +0200
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Charan Teja Kalla <charan.kalla@....qualcomm.com>,
        Krzysztof Kozlowski <krzk@...nel.org>,
        Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
        Bryan O'Donoghue <bod@...nel.org>,
        Bryan O'Donoghue <bod.linux@...w.ie>,
        Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: 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 10/9/25 7:23 AM, Charan Teja Kalla wrote:
> 
> 
> On 10/9/2025 6:02 AM, Krzysztof Kozlowski wrote:
>>> If it is legitimate meta-data for the SMMU setup then why _shouldn't_ it 
>>> go into the DT ?
>>>
>> We talked about this two or three months ago. I don't understand why you
>> just ignored that entire part and come with new binding just to not
>> touch iommu code. List of entries in iommu must have strict order, just
>> like for every other list, and you should rely on that.
> Hi Krzysztof,
> 
> I want to understand a bit more about the statement -- "List of entries
> in iommu must have strict order."
> 
> per my understanding:
> iommus = <&apps_smmu sid1 mask1>, <&apps_smmu sid2 mask2>;
> 
>      and
> 
> iommus = <&apps_smmu sid2 mask2>, <&apps_smmu sid1 mask1>;
> 
> The end result is same with no breakage as they still end up in using
> the same translation unit, i.e., ordering doesn't matter.
> 
> May be you imply something else(may be ABI[1]) here about the order,
> which I am unable to catch...

Krzysztof is referring to the 'items:' blocks in dt-bindings always
containing an ordered list of entries (i.e. the examples you gave
are NOT identical from the bindings perspective even if Linux
happens to treat them in the same way as of right now)

Konrad