-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Window write support for SSD1673 #11351
Window write support for SSD1673 #11351
Conversation
Codecov Report
@@ Coverage Diff @@
## master #11351 +/- ##
=======================================
Coverage 48.17% 48.17%
=======================================
Files 281 281
Lines 43362 43362
Branches 10393 10393
=======================================
Hits 20889 20889
Misses 18318 18318
Partials 4155 4155 Continue to review full report at Codecov.
|
e6acc6c
to
76061bc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for doc changes
@jfischer-phytec-iot any input? |
include/display.h
Outdated
@@ -48,6 +48,10 @@ enum display_screen_info { | |||
* Electrophoretic Display. | |||
*/ | |||
SCREEN_INFO_EPD = BIT(2), | |||
/** | |||
* Screen has two alternating ram buffers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we do multiple writes to one buffer and then trigger update?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No currently there is no display_flush
function available in the display API.
But SCREEN_INFO_DOUBLE_BUFFER
is jut an indication to the higher layers, e.g. incase only a partial update of the display buffer is performed the same partial update needs to happen on the second buffer to keep the display content consistent.
76061bc
to
f8421d3
Compare
2dba962
to
5a7cd31
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please split 171c4f440d392618e905eec78d4762ae457476c5 in logical peaces and remove unnecessary code changes, keep the driver design and structure.
ee00298
to
4a7db51
Compare
@jfischer-phytec-iot Splitted commits as requested and provided replies where needed |
93af899
to
4326dbc
Compare
@jfischer-phytec-iot feedback please |
Moved the overlay configuration files to board directory. Signed-off-by: Jan Van Winkel <[email protected]>
Set width, height and pitch dimensions in character framebuffer before calling display write API. Signed-off-by: Jan Van Winkel <[email protected]>
Allow to set supported pixel format in ssd1306 & ssd1673 drivers Signed-off-by: Jan Van Winkel <[email protected]>
Added missing API function set_orientation to ssd1306 & ssd1673 drivers. Signed-off-by: Jan Van Winkel <[email protected]>
Return correct error codes in SSD1673 driver instead of -1 Signed-off-by: Jan Van Winkel <[email protected]>
Clear SSD1673 display during display driver initialization instead of triggering clear via setting contrast. Signed-off-by: Jan Van Winkel <[email protected]>
Added support to the SSD1673 dipslay for partially writing the display Signed-off-by: Jan Van Winkel <[email protected]>
Added missing README.rst for character frame buffer sample Signed-off-by: Jan Van Winkel <[email protected]>
4326dbc
to
bfb11c9
Compare
@jfischer-phytec-iot any further input? |
Added support for writing to a window instead of the complete display