From: Will Deacon <will@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>
Cc: joro@8bytes.org, 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 v8 3/7] iommu: Add verisilicon IOMMU driver
Date: Tue, 9 Sep 2025 14:12:03 +0100 [thread overview]
Message-ID: <aMAno-DkDJumcAtj@willie-the-truck> (raw)
In-Reply-To: <20250827090809.34555-4-benjamin.gaignard@collabora.com>
On Wed, Aug 27, 2025 at 11:07:59AM +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>
> ---
> changes in version 8:
> - Add API to restore VSI iommu context from decoder driver
> - Fix reported checkpatch issues: add comment in pinlock_t declaration
> and remove blank line.
>
> drivers/iommu/Kconfig | 11 +
> drivers/iommu/Makefile | 1 +
> drivers/iommu/vsi-iommu.c | 810 ++++++++++++++++++++++++++++++++++++++
> include/linux/vsi-iommu.h | 21 +
> 4 files changed, 843 insertions(+)
> create mode 100644 drivers/iommu/vsi-iommu.c
> create mode 100644 include/linux/vsi-iommu.h
I still object to the duplication with the rockchip driver:
https://lore.kernel.org/all/aH5yR9CkYSJ4PaZV@willie-the-truck/
at least drop me from cc if you're going to ignore my comments, please.
Will
next prev parent reply other threads:[~2025-09-09 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 9:07 [PATCH v8 0/7] Add support for Verisilicon IOMMU used by media codec blocks Benjamin Gaignard
2025-08-27 9:07 ` [PATCH v8 1/7] dt-bindings: vendor-prefixes: Add Verisilicon Benjamin Gaignard
2025-08-27 9:07 ` [PATCH v8 2/7] dt-bindings: iommu: verisilicon: Add binding for VSI IOMMU Benjamin Gaignard
2025-08-27 9:07 ` [PATCH v8 3/7] iommu: Add verisilicon IOMMU driver Benjamin Gaignard
2025-09-09 13:12 ` Will Deacon [this message]
2025-08-27 9:08 ` [PATCH v8 4/7] MAINTAINERS: Add entry for Verisilicon " Benjamin Gaignard
2025-08-27 9:08 ` [PATCH v8 5/7] media: verisilicon: AV1: Restore IOMMU context before decoding a frame Benjamin Gaignard
2025-08-27 9:08 ` [PATCH v8 6/7] arm64: dts: rockchip: Add verisilicon IOMMU node on RK3588 Benjamin Gaignard
2025-08-27 9:08 ` [PATCH v8 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=aMAno-DkDJumcAtj@willie-the-truck \
--to=will@kernel.org \
--cc=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