[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b25aa269-6dc8-43d4-a3f3-85691ace134e@collabora.com>
Date: Thu, 23 Oct 2025 11:42:46 +0300
From: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
To: Dmitry Osipenko <dmitry.osipenko@...labora.com>,
Sandy Huang <hjc@...k-chips.com>, Heiko Stübner
<heiko@...ech.de>, Andy Yan <andy.yan@...k-chips.com>,
Robin Murphy <robin.murphy@....com>,
Sebastian Reichel <sebastian.reichel@...labora.com>,
Daniel Stone <daniels@...labora.com>
Cc: kernel@...labora.com, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH v1] drm/rockchip: Set VOP for the DRM DMA device
On 10/22/25 7:19 PM, Dmitry Osipenko wrote:
> Use VOP for DMA operations performed by DRM core. Rockchip DRM driver
> is backed by a virtual device that isn't IOMMU-capable, while VOP is the
> actual display controller device backed by IOMMU. Fixes "swiotlb buffer
> is full" warning messages originated from GEM prime code paths.
>
> Note, that backporting is non-trivial as this depends on 143ec8d3f9396
> ("drm/prime: Support dedicated DMA device for dma-buf imports"), which
> landed in v6.16 and 421be3ee36a4 ("drm/rockchip: Refactor IOMMU
> initialisation"), which landed in v5.19.
>
> Reported-by: Daniel Stone <daniels@...labora.com>
> Fixes: 2048e3286f34 ("drm: rockchip: Add basic drm driver")
> Cc: stable@...r.kernel.org # v6.16+
> Reviewed-by: Sebastian Reichel <sebastian.reichel@...labora.com>
> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@...labora.com>
> ---
With the patch applied I'm not able to fire those warnings anymore - tested on
my ROCK 5B (RK3588) and ROCK 4D (RK3576) boards. Hence you may add:
Tested-by: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
Powered by blists - more mailing lists