Skip to content

Conversation

heronet
Copy link
Contributor

@heronet heronet commented Oct 20, 2025

Add driver for HUB12 interface monochrome LED matrix displays.

Features:

  • 32x16 pixel resolution, 1-bit monochrome (PIXEL_FORMAT_MONO01)
  • SPI-based data transfer with shift registers
  • Configurable brightness control
  • Thread-safe framebuffer access with semaphore

The driver implements the standard Zephyr display API

Add device tree binding for HUB12 interface monochrome LED matrix
displays (32x16 pixels).

The HUB12 interface uses SPI for data transfer to shift registers,
with additional GPIO pins for row address selection (PA, PB),
output enable (PE), and data latching (PLAT).

Signed-off-by: Siratul Islam <[email protected]>
@heronet heronet force-pushed the drivers/display/add-hub12-matrix branch from ceee1e6 to f1c8199 Compare October 20, 2025 12:02
Comment on lines 8 to 9
depends on SPI
depends on GPIO
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed it. Thanks

Add driver for HUB12 interface monochrome LED matrix displays.

Features:
- 32x16 pixel resolution, 1-bit monochrome (PIXEL_FORMAT_MONO01)
- SPI-based data transfer with shift registers
- Configurable brightness control
- Thread-safe framebuffer access with semaphore

The driver implements the standard Zephyr display API

Signed-off-by: Siratul Islam <[email protected]>
@heronet heronet force-pushed the drivers/display/add-hub12-matrix branch from f1c8199 to a8f5a64 Compare October 20, 2025 14:13
@heronet heronet requested a review from maass-hamburg October 20, 2025 14:13
Copy link

with additional GPIO pins for row address selection (PA, PB),
output enable (PE), and data latching (PLAT).

compatible: "hub12"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Has to be vendor, device. Also use the specific chip, that is used, if there are multiple chips, use the one that this is based (the original not the clones) on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants