[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84d0a611-586e-4e28-9be5-ef2cb58391cf@kernel.org>
Date: Thu, 9 Oct 2025 17:14:12 +0900
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Charan Teja Kalla <charan.kalla@....qualcomm.com>,
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: 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 14:23, 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."
See writing bindings (and countless of reviews on the mailing lists).
Best regards,
Krzysztof
Powered by blists - more mailing lists