Skip to content

Conversation

@hydra
Copy link

@hydra hydra commented Jan 20, 2026

Description

ST7565 - Only render if the display is active.

If the display is off, no-need to render, just wastes power and cpu-cycles. Also prevents accidental use the LCD when not active.

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout (addition or update)
  • Documentation

Issues Fixed or Closed by This PR

  • None

Checklist

  • My code follows the code style of this project: C, Python
  • I have read the PR Checklist document and have made the appropriate changes.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

@github-actions github-actions bot added the core label Jan 20, 2026
@drashna drashna requested a review from a team January 23, 2026 03:00

void st7565_render(void) {
if (!st7565_initialized) {
if (!st7565_initialized || !st7565_active) {
Copy link
Member

Choose a reason for hiding this comment

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

This will break the existing behaviour of "writing to the display when its timed out, will turn back on the display".

Copy link
Author

Choose a reason for hiding this comment

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

other code probably shouldn't be relying on that side-effect.

suggest we find occurences of this and call some method to activate the display prior to writing to it where this happens.

e.g. (psuedo-code)

st7565_setActive();
st7565_write(...);

do you know where this behavior relied upon in the codebase?

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants