]> git.donarmstrong.com Git - qmk_firmware.git/commit
Autodetect lack of screen presence
authorTerryMathews <terry@terrymathews.net>
Sun, 26 Aug 2018 17:12:41 +0000 (13:12 -0400)
committerJack Humbert <jack.humb@gmail.com>
Thu, 30 Aug 2018 01:03:23 +0000 (21:03 -0400)
commitd12d058baeb1f26a05077f88406bc3222f185129
treeb41930947ca634ee84ab01f09ec64fb125fd437c
parent972388447b03e1c403f20acd6c6b04363864f66e
Autodetect lack of screen presence

This is the simplest, most efficient way I could come up with to silence
the "Failed to start write 60" error that occurs when QMK tries to talk
to a screen that doesn't exist.

iota_gfx_init passes a success boolean. We catch that into a global bool
(we could rewrite multiple functions to pass this as an argument, but
given the number of keyboards using this code it seemed less disruptive
this way) and then use that as a conditional on running the
iota_gfx_task in matrix_scan_user.

Tl;dr: if the screen doesn't init, the screen write code doesn't run.
keyboards/tkc1800/keymaps/default/keymap.c
keyboards/tkc1800/keymaps/wkl/keymap.c