From: Philipp Zabel <p.zabel@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH v2 2/3] graphic_utils: add optional damage tracking
Date: Wed, 5 Apr 2023 14:27:33 +0200 [thread overview]
Message-ID: <20230405122734.2348025-2-p.zabel@pengutronix.de> (raw)
In-Reply-To: <20230405122734.2348025-1-p.zabel@pengutronix.de>
Annotate framebuffer updates with damage rectangles so drivers may
implement partial updates for displays with an integrated framebuffer.
This can speed up fbconsole.
Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
---
v2: call fb_damage() in graphic_utils instead of fbconsole
---
lib/gui/graphic_utils.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/lib/gui/graphic_utils.c b/lib/gui/graphic_utils.c
index 92f249e722bc..d91a7f355051 100644
--- a/lib/gui/graphic_utils.c
+++ b/lib/gui/graphic_utils.c
@@ -313,6 +313,12 @@ void gu_screen_blit_area(struct screen *sc, int startx, int starty, int width,
{
struct fb_info *info = sc->info;
int bpp = info->bits_per_pixel >> 3;
+ struct fb_rect rect = {
+ .x1 = startx,
+ .y1 = starty,
+ .x2 = startx + width,
+ .y2 = starty + height,
+ };
if (info->screen_base_shadow) {
int y;
@@ -325,14 +331,24 @@ void gu_screen_blit_area(struct screen *sc, int startx, int starty, int width,
fboff += sc->info->line_length;
}
}
+
+ fb_damage(info, &rect);
}
void gu_screen_blit(struct screen *sc)
{
struct fb_info *info = sc->info;
+ struct fb_rect rect = {
+ .x1 = 0,
+ .y1 = 0,
+ .x2 = info->xres,
+ .y2 = info->yres,
+ };
if (info->screen_base_shadow)
memcpy(info->screen_base, info->screen_base_shadow, sc->fbsize);
+
+ fb_damage(info, &rect);
}
void gu_fill_rectangle(struct screen *sc,
--
2.39.2
next prev parent reply other threads:[~2023-04-05 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 12:27 [PATCH v2 1/3] video: fb: " Philipp Zabel
2023-04-05 12:27 ` Philipp Zabel [this message]
2023-04-05 12:27 ` [PATCH v2 3/3] video: mipi_dbi: add damage tracking and partial updates Philipp Zabel
2023-04-11 12:02 ` [PATCH v2 1/3] video: fb: add optional damage tracking Sascha Hauer
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=20230405122734.2348025-2-p.zabel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=barebox@lists.infradead.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