| Message ID | 20230103215004.22646-5-agraf@csgraf.de |
|---|---|
| State | Superseded |
| Delegated to: | Anatolij Gustschin |
| Headers | show |
| Series | Add video damage tracking | expand |
On Tue, 3 Jan 2023 at 14:50, Alexander Graf <agraf@csgraf.de> wrote: > > Let's report the video damage when we draw a bitmap on the screen. This > way we can later lazily flush only relevant regions to hardware. > > Signed-off-by: Alexander Graf <agraf@csgraf.de> > Reported-by: Da Xue <da@libre.computer> > --- > drivers/video/video_bmp.c | 2 ++ > 1 file changed, 2 insertions(+) > Reviewed-by: Simon Glass <sjg@chromium.org>
diff --git a/drivers/video/video_bmp.c b/drivers/video/video_bmp.c index 6188a13e44..7dc5b011a8 100644 --- a/drivers/video/video_bmp.c +++ b/drivers/video/video_bmp.c @@ -424,6 +424,8 @@ int video_bmp_display(struct udevice *dev, ulong bmp_image, int x, int y, break; }; + video_damage(dev, x, y, width, height); + /* Find the position of the top left of the image in the framebuffer */ fb = (uchar *)(priv->fb + y * priv->line_length + x * bpix / 8); ret = video_sync_copy(dev, start, fb);
Let's report the video damage when we draw a bitmap on the screen. This way we can later lazily flush only relevant regions to hardware. Signed-off-by: Alexander Graf <agraf@csgraf.de> Reported-by: Da Xue <da@libre.computer> --- drivers/video/video_bmp.c | 2 ++ 1 file changed, 2 insertions(+)