dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-fbdev@vger.kernel.org, David Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH resend 0/5] video: fbdev: ssd1307fb: Optimizations and improvements
Date: Mon, 19 Jul 2021 21:23:29 +0200	[thread overview]
Message-ID: <YPXRMXQxCW+Agaz8@ravnborg.org> (raw)
In-Reply-To: <20210714145804.2530727-1-geert@linux-m68k.org>

Hi Geert,

On Wed, Jul 14, 2021 at 04:57:59PM +0200, Geert Uytterhoeven wrote:
> 	Hi all,
> 
> This patch series optimizes console operations on ssd1307fb, after the
> customary fixes and cleanups.
> 
> Currently, each screen update triggers an I2C transfer of all screen
> data, up to 1 KiB of data for a 128x64 display, which takes at least 20
> ms in Fast mode.  While many displays are smaller, and thus require less
> data to be transferred, 20 ms is still an optimistic value, as the
> actual data transfer may be much slower, especially on bitbanged I2C
> drivers.  After this series, the amount of data transfer is reduced, as
> fillrect, copyarea, and imageblit only update the rectangle that
> changed.
> 
> This has been tested on an Adafruit FeatherWing OLED with an SSD1306
> controller and a 128x32 OLED, connected to an OrangeCrab ECP5 FPGA board
> running a 64 MHz VexRiscv RISC-V softcore, where it reduced the CPU
> usage for blinking the cursor from more than 70% to ca. 10%.
> 
> Thanks for your comments!
> 
> Geert Uytterhoeven (5):
>   video: fbdev: ssd1307fb: Propagate errors via
>     ssd1307fb_update_display()
>   video: fbdev: ssd1307fb: Simplify ssd1307fb_update_display()
>   video: fbdev: ssd1307fb: Extract ssd1307fb_set_address_range()
>   video: fbdev: ssd1307fb: Optimize screen updates
>   video: fbdev: ssd1307fb: Cache address ranges

A few comments left for a couple of patches.
The remaining patches are:
Acked-by: Sam Ravnborg <sam@ravnborg.org>

Do you have commit rights to drm-misc-next?

	Sam

  parent reply	other threads:[~2021-07-19 19:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 14:57 [PATCH resend 0/5] video: fbdev: ssd1307fb: Optimizations and improvements Geert Uytterhoeven
2021-07-14 14:58 ` [PATCH resend 1/5] video: fbdev: ssd1307fb: Propagate errors via ssd1307fb_update_display() Geert Uytterhoeven
2021-07-14 14:58 ` [PATCH resend 2/5] video: fbdev: ssd1307fb: Simplify ssd1307fb_update_display() Geert Uytterhoeven
2021-07-19 19:05   ` Sam Ravnborg
2021-07-20  7:43     ` Geert Uytterhoeven
2021-07-20 14:41       ` Sam Ravnborg
2021-07-14 14:58 ` [PATCH resend 3/5] video: fbdev: ssd1307fb: Extract ssd1307fb_set_address_range() Geert Uytterhoeven
2021-07-19 19:07   ` Sam Ravnborg
2021-07-20  7:51     ` Geert Uytterhoeven
2021-07-14 14:58 ` [PATCH resend 4/5] video: fbdev: ssd1307fb: Optimize screen updates Geert Uytterhoeven
2021-07-19 19:21   ` Sam Ravnborg
2021-07-20  7:56     ` Geert Uytterhoeven
2021-07-20  9:16       ` Geert Uytterhoeven
2021-07-20 14:39         ` Sam Ravnborg
2021-07-14 14:58 ` [PATCH resend 5/5] video: fbdev: ssd1307fb: Cache address ranges Geert Uytterhoeven
2021-07-14 15:27 ` [PATCH resend 0/5] video: fbdev: ssd1307fb: Optimizations and improvements Sam Ravnborg
2021-07-15  6:54   ` Geert Uytterhoeven
2021-07-20 14:53     ` Daniel Vetter
2021-07-19 19:23 ` Sam Ravnborg [this message]
2021-07-20  7:33   ` Geert Uytterhoeven
2021-07-20 14:45     ` Sam Ravnborg

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=YPXRMXQxCW+Agaz8@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).