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: <e8dfad82-ab07-40e9-9296-859168142611@kernel.org>
Date: Thu, 9 Oct 2025 19:45:28 +0900
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Vikash Garodia <quic_vgarodia@...cinc.com>,
 Bryan O'Donoghue <bod@...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>,
 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 19:40, Vikash Garodia wrote:
> 
> On 10/9/2025 2:41 PM, Krzysztof Kozlowski wrote:
>> On 09/10/2025 17:38, Bryan O'Donoghue wrote:
>>> On 09/10/2025 02:04, Krzysztof Kozlowski wrote:
>>>>> The iommu description for this platform basically lacks the data that
>>>>> _should_ be there -> FUNCTION_ID.
>>>> No. The index tells that already.
>>>
>>> Hmm.
>>>>> The rule is that the DT should really describe the hardware right ?
>>>> It already does. Same as I wrote on IRC, DT already has all the
>>>> information. Entry 0 has function ID-foo. Entry 1 has function ID-bar.
>>>> Entry 2 has function ID-bar or whatever.
>>>
>>> That's the part I don't believe is true its a 1:Many relationship 
>>> between FUNCTION_ID:SIDs
>>>
>>> Let me check the docs...
>>>
>>> Here's the example I gave on IRC for lore
>>>
>>> SID 0x1940 maps to AC_VM_HLOS (Linux)
>>> SID 0x1941 maps to AC_VM_CP_BITSTREAM - protected bitstream
>>> SID 0x1945 maps to AC_WM_CP_BITSTREAM
>>>
>>
>> I responded to this on IRC... Nothing proves here that 1:many cannot be
>> done.
> 
> Kaanapali already has 1:Many relationship for FUNCTION_ID:SIDs.

Sun is a star. How is that related? I am not going to duplicate
arguments from IRC, especially to that pointless argument. Read again
discussion on IRC.

Best regards,
Krzysztof