[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6c6f6bc9-7c34-4961-8b5e-e6d02c4b2f6d@linaro.org>
Date: Fri, 4 Jul 2025 23:44:45 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Krzysztof Kozlowski <krzk@...nel.org>,
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 04/07/2025 17:45, Dmitry Baryshkov wrote:
> What about instead:
>
> - keep IOMMU entries as is
ack
> - Add iommu-maps, mapping the non-pixel SID
> - In future expand iommu-maps, describing the secure contexts?
Interesting, we are _adding_ so that's not an ABI break and if I'm
reading the documentation right, there's no hard rule on what iommu-map
defines i.e. nothing to preclude us from encoding the information we
want here.
This might work.
drivers/pci/controller/dwc/pcie-qcom.c::qcom_pcie_config_sid_1_9_0()
You can register your platform device to the SID map you parse.
Worth an experiment.
---
bod
Powered by blists - more mailing lists