Skip to content

display: carry all i8080 panel pins in the proto (wr/rd strobes + Add.pin_power)#208

Open
tyeth-ai-assisted wants to merge 1 commit into
adafruit:api-v2from
tyeth-ai-assisted:add/i8080-display-pins
Open

display: carry all i8080 panel pins in the proto (wr/rd strobes + Add.pin_power)#208
tyeth-ai-assisted wants to merge 1 commit into
adafruit:api-v2from
tyeth-ai-assisted:add/i8080-display-pins

Conversation

@tyeth-ai-assisted

Copy link
Copy Markdown

Per review on adafruit/Adafruit_Wippersnapper_Arduino#936 (the LilyGo T-Display-S3 i8080 display support): every pin in a board's display magic config should come through the protobuf, with no board-hardcoded pins in the firmware.

  • I8080PinDescriptor gains pin_wr = 12 / pin_rd = 13 — the 8080 bus strobes belong to the interface descriptor like every other bus pin (rd may be empty when not wired).
  • Add gains an optional pin_power = 12 — panel power-enable, driven high before init (e.g. the T-Display-S3 gates the panel rail on GPIO15).
  • Backlight already rides Add.backlight (BacklightConfig, digitalio/pwm oneof) — unchanged.
  • display.options: max_size:6 for the three new pin strings.

With these, the LilyGo magic config (d0–d7 / cs / dc / wr / rd / rst / backlight / powerOn) maps 1:1 onto the proto. Firmware side (nanopb regen + driver wiring, removing the I8080_* board macros) is on adafruit/Adafruit_Wippersnapper_Arduino#936; verified end-to-end on real hardware via the HIL bench.

🤖 Generated with Claude Code

I8080PinDescriptor gains pin_wr(12)/pin_rd(13) — the 8080 bus strobes belong to
the interface descriptor like every other bus pin. Add gains an optional
pin_power(12) panel power-enable (driven high before init; boards like the
LilyGo T-Display-S3 gate the panel rail on a GPIO). Backlight already rides
Add.backlight (BacklightConfig). With these, a board's display magic config
(d0-d7/cs/dc/wr/rd/rst/backlight/powerOn) maps 1:1 onto the protobuf and the
firmware needs no board-hardcoded display pins.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants