[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fa3c1732-328d-46a2-8514-2e7f9ca6c63f@kernel.org>
Date: Tue, 14 Oct 2025 21:49:17 +0100
From: Bryan O'Donoghue <bod@...nel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Robin Murphy <robin.murphy@....com>,
Charan Teja Kalla <charan.kalla@....qualcomm.com>, joro@...tes.org,
will@...nel.org, saravanak@...gle.com, conor+dt@...nel.org, robh@...nel.org,
mchehab@...nel.org, krzk+dt@...nel.org, abhinav.kumar@...ux.dev,
vikash.garodia@....qualcomm.com, dikshita.agarwal@....qualcomm.com,
Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
bjorn.andersson@....qualcomm.com, linux-media@...r.kernel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, iommu@...ts.linux.dev
Subject: Re: [RFC PATCH 0/3] Introduce iommu-map-masked for platform devices
On 14/10/2025 19:35, Dmitry Baryshkov wrote:
>> Each function id can be associated with a device and a compat string
>> associated with it.
> So, which part of the hardware is described by the -cb device? What does
> it mean_here_?
The non-pixel path video encoder, the tz video encoder...
What's not clear about that ?
---
bod
Powered by blists - more mailing lists