From: Benjamin Gaignard <benjamin.gaignard@collabora.com>
To: "Jörg Rödel" <joro@8bytes.org>
Cc: robin.murphy@arm.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, heiko@sntech.de,
nicolas.dufresne@collabora.com, jgg@ziepe.ca,
p.zabel@pengutronix.de, mchehab@kernel.org,
iommu@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com,
linux-media@vger.kernel.org
Subject: Re: [PATCH v9 3/7] iommu: Add verisilicon IOMMU driver
Date: Fri, 12 Sep 2025 14:33:06 +0200 [thread overview]
Message-ID: <f009ff62-abbe-4305-91ca-9cc762ca4fb1@collabora.com> (raw)
In-Reply-To: <vrngq76nnms3jyl5hnxqnkimjc6kil66o6fdyqn5vm3fpovmja@cfynipjw7ktp>
Le 12/09/2025 à 13:47, Jörg Rödel a écrit :
> On Thu, Sep 11, 2025 at 05:57:13PM +0200, Benjamin Gaignard wrote:
>> The Verisilicon IOMMU hardware block can be found in combination
>> with Verisilicon hardware video codecs (encoders or decoders) on
>> different SoCs.
>> Enable it will allow us to use non contiguous memory allocators
>> for Verisilicon video codecs.
>>
>> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
>> ---
>> drivers/iommu/Kconfig | 11 +
>> drivers/iommu/Makefile | 1 +
>> drivers/iommu/vsi-iommu.c | 808 ++++++++++++++++++++++++++++++++++++++
>> include/linux/vsi-iommu.h | 21 +
>> 4 files changed, 841 insertions(+)
>> create mode 100644 drivers/iommu/vsi-iommu.c
>> create mode 100644 include/linux/vsi-iommu.h
> This will not go in before Will Deacons comment about code duplication with the
> Rockchip driver is addressed.
It isn't the same hardware block, not from the same IP vendor and the bits set aren't the same.
pm_runtime, clock, spin_lock aren't managed differently.
The common point is they both use 2-level page table.
VSI iommu need an additional function to restore iommu context before decoding
each frame, rockchip doesn't need it.
Regards,
Benjamin
>
> Joerg
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-09-12 12:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 15:57 [PATCH v9 0/7] Add support for Verisilicon IOMMU used by media codec blocks Benjamin Gaignard
2025-09-11 15:57 ` [PATCH v9 1/7] dt-bindings: vendor-prefixes: Add Verisilicon Benjamin Gaignard
2025-09-11 15:57 ` [PATCH v9 2/7] dt-bindings: iommu: verisilicon: Add binding for VSI IOMMU Benjamin Gaignard
2025-09-11 15:57 ` [PATCH v9 3/7] iommu: Add verisilicon IOMMU driver Benjamin Gaignard
2025-09-12 11:47 ` Jörg Rödel
2025-09-12 12:33 ` Benjamin Gaignard [this message]
2025-09-12 17:37 ` Nicolas Dufresne
2025-09-12 18:32 ` Jason Gunthorpe
2025-09-13 5:58 ` Jörg Rödel
2025-09-15 22:58 ` Jason Gunthorpe
2025-09-16 8:48 ` Will Deacon
2025-09-16 9:30 ` Benjamin Gaignard
2025-09-16 13:02 ` Jason Gunthorpe
2025-12-12 3:31 ` Jianfeng Liu
2025-12-12 8:51 ` Benjamin Gaignard
2025-09-11 15:57 ` [PATCH v9 4/7] MAINTAINERS: Add entry for Verisilicon " Benjamin Gaignard
2025-09-11 15:57 ` [PATCH v9 5/7] media: verisilicon: AV1: Restore IOMMU context before decoding a frame Benjamin Gaignard
2025-09-11 15:57 ` [PATCH v9 6/7] arm64: dts: rockchip: Add verisilicon IOMMU node on RK3588 Benjamin Gaignard
2025-09-11 15:57 ` [PATCH v9 7/7] arm64: defconfig: enable Verisilicon IOMMU for Rockchip RK3588 Benjamin Gaignard
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=f009ff62-abbe-4305-91ca-9cc762ca4fb1@collabora.com \
--to=benjamin.gaignard@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
/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