From: Bryan O'Donoghue <bod@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
Charan Teja Kalla <charan.kalla@oss.qualcomm.com>,
joro@8bytes.org, will@kernel.org, saravanak@google.com,
conor+dt@kernel.org, robh@kernel.org, mchehab@kernel.org,
krzk+dt@kernel.org, abhinav.kumar@linux.dev,
vikash.garodia@oss.qualcomm.com,
dikshita.agarwal@oss.qualcomm.com,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
bjorn.andersson@oss.qualcomm.com, linux-media@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [RFC PATCH 0/3] Introduce iommu-map-masked for platform devices
Date: Tue, 14 Oct 2025 21:49:17 +0100 [thread overview]
Message-ID: <fa3c1732-328d-46a2-8514-2e7f9ca6c63f@kernel.org> (raw)
In-Reply-To: <6gx74wxie4wcabq27wo5y7v36uuurez4jxlzanroepqazdlgtw@sdtv2ld47d3q>
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
next prev parent reply other threads:[~2025-10-14 20:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 17:17 [RFC PATCH 0/3] Introduce iommu-map-masked for platform devices Charan Teja Kalla
2025-09-28 17:17 ` [RFC PATCH 1/3] dtbindings: add binding for iommu-map-masked property Charan Teja Kalla
2025-09-28 17:17 ` [RFC PATCH 2/3] of: create a wrapper for of_map_id() Charan Teja Kalla
2025-09-28 17:17 ` [RFC PATCH 3/3] of: implment the 'iommu-map-masked' to represent multi-functional devices Charan Teja Kalla
2025-09-28 20:23 ` [RFC PATCH 0/3] Introduce iommu-map-masked for platform devices Rob Herring
2025-10-09 0:26 ` Krzysztof Kozlowski
2025-10-09 12:16 ` Robin Murphy
2025-10-09 13:16 ` Dmitry Baryshkov
2025-10-09 13:14 ` Dmitry Baryshkov
2025-10-09 3:05 ` Vikash Garodia
2025-09-29 10:20 ` Robin Murphy
2025-10-08 19:10 ` Charan Teja Kalla
2025-10-09 10:46 ` Robin Murphy
2025-10-09 13:19 ` Dmitry Baryshkov
2025-10-09 17:03 ` Robin Murphy
2025-10-09 18:25 ` Dmitry Baryshkov
2025-10-10 19:53 ` Charan Teja Kalla
2025-10-10 22:30 ` Rob Herring
2025-10-11 0:54 ` Dmitry Baryshkov
2025-10-12 20:44 ` Bryan O'Donoghue
2025-10-12 21:57 ` Bryan O'Donoghue
2025-10-12 22:47 ` Dmitry Baryshkov
2025-10-13 10:18 ` Bryan O'Donoghue
2025-10-13 11:20 ` Robin Murphy
2025-10-13 12:31 ` Dmitry Baryshkov
2025-10-14 14:07 ` Robin Murphy
2025-10-14 18:33 ` Dmitry Baryshkov
2025-10-15 8:32 ` Charan Teja Kalla
2025-10-19 12:13 ` Dmitry Baryshkov
2025-10-14 15:07 ` Bryan O'Donoghue
2025-10-14 18:35 ` Dmitry Baryshkov
2025-10-14 20:49 ` Bryan O'Donoghue [this message]
2025-10-14 22:18 ` Dmitry Baryshkov
2025-10-15 8:53 ` Bryan O'Donoghue
2025-10-15 21:55 ` Rob Herring
2025-10-14 22:38 ` Dmitry Baryshkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa3c1732-328d-46a2-8514-2e7f9ca6c63f@kernel.org \
--to=bod@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=charan.kalla@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=saravanak@google.com \
--cc=vikash.garodia@oss.qualcomm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).