Changeset 8aef01c in mainline for uspace/srv/hid/display/main.c

Timestamp:

2020-06-07T10:18:14Z (4 years ago)

Author:

Jiri Svoboda <jiri@…>

Branches:

lfn, master, serial, ticket/834-toolchain-update, topic/msim-upgrade, topic/simplify-dev-export

Children:

a65b0c8

Parents:

6301a24f

git-author:

Jiri Svoboda <jiri@…> (2020-06-07 10:11:32)

git-committer:

Jiri Svoboda <jiri@…> (2020-06-07 10:18:14)

Message:

Configurable display double-buffering

On by default (since turning off creates flicker in the absence of
front-to-back rendering). This is the quick and dirty way: display
server renders locally to a bitmap (using mem GC) and renders the
bitmap when ready.

The more sophisticated way would be to implement buffering in the
display device. That would require, however, enhancing the protocols
to communicate frame boundaries.

File:

• uspace/srv/hid/display/main.c (modified) (2 diffs)

uspace/srv/hid/display/main.c

@@ -59 +59 @@
 static void display_client_ev_pending(void *);
 
+#ifdef CONFIG_DISP_DOUBLE_BUF
+/*
+ * Double buffering is one way to provide flicker-free display.
+ */
+static ds_display_flags_t disp_flags = df_disp_double_buf;
+#else
+/*
+ * With double buffering disabled, wet screen flicker since front-to-back
+ * rendering is not implemented.
+ */
+static ds_display_flags_t disp_flags = df_none;
+#endif
+
 static ds_client_cb_t display_client_cb = {
         .ev_pending = display_client_ev_pending
@@ -81 +94 @@
         log_msg(LOG_DEFAULT, LVL_DEBUG, "display_srv_init()");
 
-        rc = ds_display_create(NULL, &disp);
+        rc = ds_display_create(NULL, disp_flags, &disp);
         if (rc != EOK)
                 goto error;