From: Icenowy Zheng <zhengxingda@iscas.ac.cn>
To: Dominique Belhachemi <domibel@debian.org>
Cc: Maxime Ripard <mripard@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Simona Vetter <simona@ffwll.ch>,
Paul Cercueil <paul@crapouillou.net>,
Michal Wilczynski <m.wilczynski@samsung.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, ganboing@gmail.com
Subject: Re: [PATCH] drm: verisilicon: support non-coherent DMA framebuffers
Date: Tue, 29 Sep 2026 15:27:12 +0800 [thread overview]
Message-ID: <84e4511ea8e3e6bdff72ce2038bf3a3272744619.camel@iscas.ac.cn> (raw)
In-Reply-To: <CAAvaLCy7jC-jFM5ZpPVeg7gKpweAW4nPKn4HXR+xpqUHD2soXQ@mail.gmail.com>
在 2026-09-28一的 01:21 -0400,Dominique Belhachemi写道:
> On Fri, Sep 11, 2026 at 11:33 AM Icenowy Zheng
> <zhengxingda@iscas.ac.cn> wrote:
> >
> > I am still thinking how to decide whether to use dirty-tracking-
> > based
> > cache coherent maintenance or writecombine/uncached mapping.
> >
> Hi Icenowy,
>
> I looked into this again and writecombine/uncached mapping is the way
> to go.
I think drm/imagination really requires it (because the correspoding
userspace driver advertises only one memory type with
`HOST_COHERENT_BIT` set), however in the future it could also add cache
maintenance support for performance reasons.
> I used Bo Gan's XPbmtUC series and Michal Wilczynski's jh7110 display
> series and finally got the integrated BXE-4-32 GPU to work.
The XPbmtUC series is problematic -- it "supports EIC7700" "with a
hypervisor", which means it cannot run on EIC7700 natively. This
severely restricts its usage.
Samuel Holland from SiFive is working on patching the PTE on-the-fly,
but that will change all code accessing PTE in the kernel and thus is a
heavy work.
P.S. For the JH7110 rascal+dust power issue, I did a try-and-error hack
at [1]. The basical register definition of this register (called
RGX_CR_POWER_EVENT) is available in their KM volcanic part (but it
seems to apply for rogue too), but the individual bits for domains are
undocumented, and the highest 8-bit seems to be some kind of multi-core
mask on Rogue.
Thanks,
Icenowy
[1]
https://github.com/Icenowy/linux/commit/09db317c9c229ef359e35463f8c08efd3e23c685
>
> https://lore.kernel.org/all/20260316060328.1173634-1-ganboing@gmail.com/
> https://lore.kernel.org/all/20260915-jh7110-clean-send-v4-0-f0e4fd6f2cc8@samsung.com/
> https://github.com/domibel/visionfive2_gpu_bringup
>
> Best
> -Dominique
next prev parent reply other threads:[~2026-09-29 7:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 4:26 Dominique Belhachemi
2026-05-05 9:03 ` Icenowy Zheng
2026-05-05 10:22 ` Chen-Yu Tsai
2026-05-05 22:25 ` Dominique Belhachemi
2026-05-06 9:01 ` Icenowy Zheng
2026-05-06 17:38 ` Dominique Belhachemi
2026-05-06 18:00 ` Icenowy Zheng
2026-05-05 9:05 ` Icenowy Zheng
2026-05-05 9:27 ` Icenowy Zheng
2026-09-11 15:33 ` Icenowy Zheng
2026-09-28 5:21 ` Dominique Belhachemi
2026-09-29 7:27 ` Icenowy Zheng [this message]
2026-09-30 5:52 ` Dominique Belhachemi
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=84e4511ea8e3e6bdff72ce2038bf3a3272744619.camel@iscas.ac.cn \
--to=zhengxingda@iscas.ac.cn \
--cc=airlied@gmail.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=domibel@debian.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ganboing@gmail.com \
--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=palmer@dabbelt.com \
--cc=paul@crapouillou.net \
--cc=pjw@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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®