Document immediate brightness architecture
This commit is contained in:
16
README.md
16
README.md
@@ -6,6 +6,21 @@ The internal display is the master. Brightness keys change the internal panel, s
|
||||
|
||||
This avoids drift from letting two outputs auto-adjust independently.
|
||||
|
||||
## Architecture
|
||||
|
||||
The real brightness change is intentionally immediate:
|
||||
|
||||
```text
|
||||
brightness-up/down-all
|
||||
-> brightnessctl immediately changes the internal display
|
||||
-> brightness-osd only displays or updates the visual feedback
|
||||
-> external-brightness-sync.service mirrors the internal percentage later
|
||||
```
|
||||
|
||||
The actual `brightnessctl` call must not be debounced. Only the OSD may be smoothed by reusing the running OSD process and extending its hide timer.
|
||||
|
||||
The external monitor is not changed in the key-binding scripts. `ddcutil` is slower than an internal backlight write, so it runs separately in the sync service.
|
||||
|
||||
## Features
|
||||
|
||||
- Internal display controlled with `brightnessctl`
|
||||
@@ -82,6 +97,7 @@ Default config:
|
||||
```bash
|
||||
BRIGHTNESS_BACKLIGHT_DEVICE="intel_backlight"
|
||||
BRIGHTNESS_SYNC_BACKLIGHT="/sys/class/backlight/intel_backlight"
|
||||
BRIGHTNESS_OSD_BACKLIGHT="/sys/class/backlight/intel_backlight"
|
||||
BRIGHTNESS_STEP="10"
|
||||
BRIGHTNESS_DDCUTIL_MODEL="HG342PCB"
|
||||
BRIGHTNESS_DDCUTIL_DISPLAY="1"
|
||||
|
||||
Reference in New Issue
Block a user