diff options
| author | Lyude Paul <lyude@redhat.com> | 2021-11-05 14:33:42 -0400 |
|---|---|---|
| committer | Lyude Paul <lyude@redhat.com> | 2021-11-17 17:36:49 -0500 |
| commit | 37fe0cf5fb803d98efd7feb64b408c9b029c1085 (patch) | |
| tree | 6d1479f594134b3200c10d16db9ce7cdfd94d195 /Documentation/devicetree/bindings/rng/st,stm32-rng.yaml | |
| parent | f58a435311672305d8747f40e35235f7ed64ae69 (diff) | |
| download | linux-stable-37fe0cf5fb803d98efd7feb64b408c9b029c1085.tar.gz linux-stable-37fe0cf5fb803d98efd7feb64b408c9b029c1085.tar.bz2 linux-stable-37fe0cf5fb803d98efd7feb64b408c9b029c1085.zip | |
drm/i915: Clarify probing order in intel_dp_aux_init_backlight_funcs()
Hooray! We've managed to hit enough bugs upstream that I've been able to
come up with a pretty solid explanation for how backlight controls are
actually supposed to be detected and used these days. As well, having the
rest of the PWM bits in VESA's backlight interface implemented seems to
have fixed all of the problematic brightness controls laptop panels that
we've hit so far.
So, let's actually document this instead of just calling the laptop panels
liars. As well, I would like to formally apologize to all of the laptop
panels I called liars. I'm sorry laptop panels, hopefully you can all
forgive me and we can move past this~
Signed-off-by: Lyude Paul <lyude@redhat.com>
Acked-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20211105183342.130810-6-lyude@redhat.com
Diffstat (limited to 'Documentation/devicetree/bindings/rng/st,stm32-rng.yaml')
0 files changed, 0 insertions, 0 deletions