Started as "capture it when we happen upon it, not full project scope" on
the assumption we'd need each controller's datasheet to explain why a
panel is active-high/low on BUSY. Turns out GxEPD2 already has this as
data, not something to derive: every vendor driver's constructor passes
its own busy_level literal to GxEPD2_EPD(cs, dc, rst, busy, busy_level,
...), which is exactly what EpdPanelDescriptor::busy_active_level
encodes per-panel here. So this is in scope to track for every panel,
not just ones we happen to touch - just not yet: pinned as a later task to
go read it off every vendor driver in one pass, rather than accreting it
incidentally the way this table has so far.
| Panel | Controller | busy_level (vendor ctor) | busy_active_level | Hardware-confirmed? |
|---|---|---|---|---|
| GDEY0213Z98 | SSD1680 | HIGH | true | yes (bench panel, working) |
| GDEQ0426T82 | SSD1677 | HIGH | true | yes (2026-09-19) |
| GDEQ0583T31 | UC8179 | LOW | false | pending |
| GDEY029F51 | JD79667 | LOW | false | no (4-color, not yet ported to this engine) |
| GDEY0579F51 | HX8717 | LOW | false | no (4-color, not yet ported to this engine) |
Source: each driver's own .cpp, GxEPD2_EPD(cs, dc, rst, busy, <level>, ...)
constructor call (grep GxEPD2_EPD(cs, dc, rst, busy in vendor/src/**/*.cpp).