[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f2v4y2fi6dw44zfp4uxn6d5v5hq4sukwds4hxn4btn6zxr7vrp@b4qbub57vgft>
Date: Mon, 19 Jan 2026 15:06:12 +0100
From: Jörg Rödel <joro@...tes.org>
To: Benjamin Gaignard <benjamin.gaignard@...labora.com>
Cc: Will Deacon <will@...nel.org>, robin.murphy@....com, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, heiko@...ech.de,
nicolas.dufresne@...labora.com, p.zabel@...gutronix.de, mchehab@...nel.org,
iommu@...ts.linux.dev, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org, linux-media@...r.kernel.org,
kernel@...labora.com
Subject: Re: [PATCH v11 3/7] iommu: Add verisilicon IOMMU driver
On Mon, Jan 19, 2026 at 11:28:11AM +0100, Benjamin Gaignard wrote:
> * This hardware block is using a 2 pages tables allocation structure.
> * That make very similar to Rockhip iommu hardware blocks but it has
> * it own driver because the registers offset and configuration bits
> * are completely different. An additional raison is that this hardware
> * has been developped by Verisilicon to be used by their hardware video
> * decoders and for a general purpose like Rockchip iommus.
Please run a spell checker on this (e.g. raion -> reason, developped ->
developed) and I think the last sentence lacks a "not". Looks good otherwise.
-Joerg
Powered by blists - more mailing lists