From: Conor Dooley <conor.dooley@microchip.com>
To: Icenowy Zheng <zhengxingda@iscas.ac.cn>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Paul Walmsley <pjw@kernel.org>,
Samuel Holland <samuel.holland@sifive.com>,
Dominique Belhachemi <domibel@debian.org>,
Michal Wilczynski <m.wilczynski@samsung.com>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, Icenowy Zheng <uwu@icenowy.me>
Subject: Re: [RFC PATCH 0/2] drm: add a noncoherent mapping checking helper
Date: Wed, 30 Sep 2026 15:18:52 +0100 [thread overview]
Message-ID: <20260930-zippy-container-d48f72432c1f@wendy> (raw)
In-Reply-To: <20260930073528.3369325-1-zhengxingda@iscas.ac.cn>
[-- Attachment #1: Type: text/plain, Size: 2527 bytes --]
On Wed, Sep 30, 2026 at 03:35:26PM +0800, Icenowy Zheng wrote:
> This patchset tries to address the lack of uncached mapping support on
> several SiFive-core-based SoCs, currently targeting JH7110 but EIC7700
> would have the same problem (although it uses DC8000 display controller
> instead of DC8200 and real display support is pending).
>
> Because other users (either SoCs with Xuantie cores, which have
> Xtheadmae extensions or non-RISC-V SoCs) of the driver have proper
> writecombine support, a helper is added to check whether coherent
> (cache-bypassing) mapping is available. This helper currently returns
> true for all architectures except RISC-V, and checks whether
> pgprot_writecombine() is a no-op on RISC-V.
>
> The patch really enabling manual cache maintenance for the verisilicon
> driver is picked from Dominique, and reworked to check both
> dma-noncoherent property and the platform's mapping capaibility.
>
> Tested on VisionFive 2 with the display enablement patchset at [1] (and
> its dependency).
>
> Also tested on Lichee Pi 4A (TH1520, which has Xtheadmae), operation is
> not affected, map_noncoherent isn't set and Xorg says kernel dirty
> updates aren't required.
>
> [1] https://patch.msgid.link/20260929-jh7110-clean-send-v5-0-82b4d8e3c6c7@samsung.com
Out of curiosity, have you seen Bo Gan's series from a few months ago
that creates an extension/erratum to get these devices working?
https://lore.kernel.org/linux-riscv/20260316060328.1173634-1-ganboing@gmail.com/
I've been meaning to reply to it over and over again for the last number
of months, but I just haven't had the time to actually understand the
detail of the EIC7700 solution or check whether it works yet. I know
this is just one driver because the JH7110 only has this problem for the
display pipeline, but according to Bo Gan this applies to all
peripherals on the EIC7700.
>
> Dominique Belhachemi (1):
> drm: verisilicon: support non-coherent DMA framebuffers
>
> Icenowy Zheng (1):
> drm: add a helper function to check availbility of coherent mapping
>
> drivers/gpu/drm/verisilicon/vs_cursor_plane.c | 9 ++++++
> drivers/gpu/drm/verisilicon/vs_drm.c | 32 ++++++++++++++++++-
> drivers/gpu/drm/verisilicon/vs_drm.h | 7 ++++
> .../gpu/drm/verisilicon/vs_primary_plane.c | 9 ++++++
> include/drm/drm_cache.h | 21 ++++++++++++
> 5 files changed, 77 insertions(+), 1 deletion(-)
>
> --
> 2.55.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-30 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 7:35 Icenowy Zheng
2026-09-30 7:35 ` [RFC PATCH 1/2] drm: add a helper function to check availbility of coherent mapping Icenowy Zheng
2026-09-30 7:35 ` [RFC PATCH 2/2] drm: verisilicon: support non-coherent DMA framebuffers Icenowy Zheng
2026-09-30 14:18 ` Conor Dooley [this message]
2026-09-30 14:38 ` [RFC PATCH 0/2] drm: add a noncoherent mapping checking helper Icenowy Zheng
2026-09-30 16:30 ` Conor Dooley
2026-10-01 5:21 ` Icenowy Zheng
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=20260930-zippy-container-d48f72432c1f@wendy \
--to=conor.dooley@microchip.com \
--cc=airlied@gmail.com \
--cc=domibel@debian.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=m.wilczynski@samsung.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pjw@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=uwu@icenowy.me \
--cc=zhengxingda@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®