Skip to content

fix(backlight): Retrieve only brightness from settings when CONFIG_ZMK_BACKLIGHT_ON_START disabled#3304

Open
kurtis-lew wants to merge 1 commit intozmkfirmware:mainfrom
kurtis-lew:fix/backlight-retrieve-brightness-only-from-settings
Open

fix(backlight): Retrieve only brightness from settings when CONFIG_ZMK_BACKLIGHT_ON_START disabled#3304
kurtis-lew wants to merge 1 commit intozmkfirmware:mainfrom
kurtis-lew:fix/backlight-retrieve-brightness-only-from-settings

Conversation

@kurtis-lew
Copy link
Copy Markdown
Contributor

On startup, when the settings subsystem loads the most recent backlight brightness and on-state, it overrides the effect of the CONFIG_ZMK_BACKLIGHT_ON_START Kconfig.

This PR creates congruency between the settings subsystem and this Kconfig by not calling zmk_backlight_update() and setting the backlight state to false when CONFIG_ZMK_BACKLIGHT_ON_START=n.

Tested on custom board.

@kurtis-lew kurtis-lew requested a review from a team as a code owner March 27, 2026 21:46
@caksoylar
Copy link
Copy Markdown
Contributor

I am pretty sure this applies to underglow as well, and has been a known behavior for some time (so is documented as such). I wouldn't have an objection to changing the behavior, but I'd like to hear opinions from other maintainers.

@kurtis-lew kurtis-lew force-pushed the fix/backlight-retrieve-brightness-only-from-settings branch from 067d1fd to 781358e Compare April 1, 2026 02:43
@petejohanson
Copy link
Copy Markdown
Contributor

Given this is established behavior, I'm wary to change this. Especially because this would now ignore the saved value for anyone who received a build with this Kconfig set but used a behavior to turn off the backlight, expecting that to persist until explicitly turned back on.

Can you help me understand your use case, so we can maybe come up with a fix that isn't a breaking change?

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.

3 participants