Skip to content

Commit 7c3b1c0

Browse files
committed
display: add frame_incomplete to display_buffer_descriptor
Introduces support for double-buffered/latched displays. Currently, every write has to be presented to the user immediately, which negates the advantage of latched displays to prevent frame tearing. Now, GUI managers can indicate whether the current `display_write` call is the last call of the frame or not, allowing displays to group writes to a single present. Signed-off-by: Martin Stumpf <[email protected]>
1 parent 40cd35e commit 7c3b1c0

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

doc/releases/release-notes-4.1.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -92,6 +92,10 @@ Drivers and Sensors
9292

9393
* Display
9494

95+
* Added flag ``frame_incomplete`` to ``display_write`` that indicates whether a write is the last
96+
write of the frame, allowing display drivers to implement double buffering / tearing enable
97+
signal handling (:github:`81250`)
98+
9599
* Ethernet
96100

97101
* Flash

include/zephyr/drivers/display.h

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -127,6 +127,8 @@ struct display_buffer_descriptor {
127127
uint16_t height;
128128
/** Number of pixels between consecutive rows in the data buffer */
129129
uint16_t pitch;
130+
/** Indicates that this is not the last write buffer of the frame */
131+
bool frame_incomplete;
130132
};
131133

132134
/**

0 commit comments

Comments
 (0)