mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	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
Subject: Re: [PATCH] drm: verisilicon: support non-coherent DMA framebuffers
Date: Wed, 06 May 2026 17:01:42 +0800	[thread overview]
Message-ID: <de419b42100ae55bfc1d6db44cac3d763c57247b.camel@iscas.ac.cn> (raw)
In-Reply-To: <CAAvaLCyZfdo+h+gYjEd6=kDug0A77rqH2e4U7JzpUEEGo_mvDA@mail.gmail.com>

在 2026-05-05二的 18:25 -0400,Dominique Belhachemi写道:
> On Tue, May 5, 2026 at 5:03 AM Icenowy Zheng
> <zhengxingda@iscas.ac.cn> wrote:
> > 
> > 在 2026-05-05二的 04:26 +0000,Dominique Belhachemi写道:
> > > Wire up the standard non-coherent path matching the ingenic DRM
> > > driver.
> > > 
> > > Tested on StarFive JH7110 (VisionFive 2 v1.3B).
> > 
> > Interesting, I am curious about other patches added to test this.
> > 
> Hi,
> 
> I tested this on Debian unstable with a slightly patched 7.0.3 kernel
> [1].
> The test branch contains your verisilicon series, Michal's JH7110
> display series [2],
> and a JH7110 ccache change [3], which was also required to
> communicate
> with the BXE-4-32 firmware [4].

BTW did you run any rendering? I think the way currently powervr open
source driver works requires "coherent memory" (although it's usually
implemented as uncached memory).

> 
> This change here is only used to remove the ugly framebuffer stripes
> on the console and in the desktop environment.

But I still think it'd be better to implement proper uncached memory
support instead of flushing caches with dirty tracking.

> 
> [1] https://github.com/domibel/linux/tree/jh7110_dc8200_hdmi_v7.0.3
> [2]
> https://lore.kernel.org/lkml/20251108-jh7110-clean-send-v1-0-06bf43bb76b1@samsung.com/
> [3]
> https://lore.kernel.org/lkml/20260430035259.3402954-1-domibel@debian.org/
> [4]
> https://github.com/domibel/linux/tree/powervr_on_jh7110_visionfive2_v7.0.3

The POW_RASCALDUST thing looks quite interesting, maybe I should
investigate it further.

Thanks,
Icenowy
> 
> Dominique


  reply	other threads:[~2026-05-06  9:02 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 [this message]
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
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=de419b42100ae55bfc1d6db44cac3d763c57247b.camel@iscas.ac.cn \
    --to=zhengxingda@iscas.ac.cn \
    --cc=airlied@gmail.com \
    --cc=domibel@debian.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.wilczynski@samsung.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=paul@crapouillou.net \
    --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®