Re: [PATCH v7 00/12] media: iris: Migrate iommus to iris sub nodes

From: Krzysztof Kozlowski

Date: Sun Nov 22 2026 - 11:42:52 EST


On 2026-11-20 16:40 +0530, Vikash Garodia wrote:
> The VPU issues DMA through several SMMU streams, and the hardware does
> not restricts specific streams with specific addressable range. The
> non-pixel stream is restricted to use 0-600MB of IOVA space, while the
> pixel stream can address the full range:
> +-----------------------------------------------------------+
> | non-pixel stream addressable range (600 MB - 3.5 GB) |
> | 0x25800000 - 0xe0000000 |
> +-----------------------------------------------------------+
> | pixel stream addressable range (0 - 3.5 GB) |
> | 0x00000000 - 0xe0000000 |
> +-----------------------------------------------------------+
>
> A single "iommus" property on the video-codec node puts every stream in
> one IOMMU domain sharing one IOVA allocator, so nothing keeps a
> non-pixel buffer inside the low 600 MB. Once an allocation lands below
> that boundary the hardware faults, which shows up as unhandled SMMU page
> faults and spontaneous reboots:
> https://gitlab.freedesktop.org/drm/msm/-/work_items/100
>
> Fix was made in iris/venus driver to reserve the 0-600MB range and
> thereby prevent iova allocation from that range.
> https://lore.kernel.org/all/20260818-reserve_iova_in_driver-v2-0-5005a1154408@xxxxxxxxxxxxxxxx
>
> Given that the address range restriction is for specific VPU stream, it
> should be ideally moved to that stream. To achieve the same, a subset
> of streams is now represented as subnodes, so that each can be
> associated with its respective addressable range.

Patchset does not apply, neither on next nor on provided base. At least
b4 review fails here. It seems that pieces of the code here might be
not complete and there are followups, so merge these follow ups here.

Best regards,
Krzysztof