drm_atomic_b...n_pre_enable(9)
drm_atomic_b...n_pre_enable(9) π β¨
okay so bestie, weβre in the Kernel API Manual and this page is literally called drm_atomic_b...n_pre_enable(9) β the full function name is giving main-character energy right below. π«Ά
πΈ NAME πΈ
drm_atomic_bridge_chain_pre_enable β prepares for enabling all bridges in the encoder chain. π
β¨ SYNOPSIS β¨
void drm_atomic_bridge_chain_pre_enable (struct drm_bridge *bridge ,
struct drm_atomic_commit *state );
π ARGUMENTS π
bridgeβ bridge control structure π«Άstateβ atomic state being committed β¨
π DESCRIPTION π
So this one calls the drm_bridge_funcs.atomic_pre_enable op for all the bridges in the encoder chain, starting from the last bridge to the first. Itβs giving reverse-order slay. π₯ These are called before calling drm_encoder_helper_funcs.atomic_enable.
If a bridge sets pre_enable_prev_first, then the pre_enable for the prev bridge will be called before pre_enable of this bridge. Thatβs the whole vibe check. π¦
π EXAMPLE π
Picture it:
Bridge A ---> Bridge B ---> Bridge C ---> Bridge D ---> Bridge E
With pre_enable_prev_first flag enable in Bridge B, D, E then the resulting pre_enable order would be, Bridge C, Bridge D, Bridge E, Bridge A, Bridge B. π
β NOTE β
tiny note, huge consequences: the bridge passed should be the one closest to the encoder. no cap. π
π SEE ALSO π
go read these next, bestie:
- Kernel file
./drivers/gpu/drm/drm_bridge.coverview(9) - display driver integration(9)
- special care dsi(9)
- dsi bridge operations(9)
- bridge chain format selection(9)
- drm_bridge_enter(9)
- drm_bridge_exit(9)
- drm_bridge_unplug(9)
- drm_bridge_get(9)
- drm_bridge_put(9)
- drm_bridge_clear_and_put(9)
- drm_bridge_put_void(9)
- drm_bridge_add(9)
- devm_drm_bridge_add(9)
- drm_bridge_remove(9)
- drm_bridge_attach(9)
- bridge operations(9)
- drm_bridge_chain_mode_valid(9)
- drm_bridge_chain_mode_set(9)
- drm_atomic_bridge_chain_disable(9)
- drm_atomic_bridge_chain_post_disable(9)
- drm_atomic_bridge_chain_enable(9)
- drm_atomic_bridge_chain_check(9)
- drm_bridge_detect(9)
- drm_bridge_get_modes(9)
- drm_bridge_edid_read(9)
- drm_bridge_hpd_enable(9)
- drm_bridge_hpd_disable(9)
- drm_bridge_hpd_notify(9)
- of_drm_find_and_get_bridge(9)
- of_drm_find_bridge(9)
- of_drm_get_bridge_by_endpoint(9)
- devm_drm_put_bridge(9)
mwah π thatβs the whole page! this one comes from the Kernel API Manual, source ./drivers/gpu/drm, date October 2026, and its page name is drm_atomic_b...n_pre_enable(9). byeee π«Άβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms