dm_test_dmub...load_timeout(9)
β¨ dm_test_dmub_hw_resume_auto_load_timeout π
okay bestie, welcome to the Kernel API Manual β this one's a KUnit test page from the DRM/AMD display corner of the kernel, and honestly it's giving "small function, big feelings" π«Ά
πΈ NAME πΈ
dm_test_dmub_hw_resume_auto_load_timeout β a test that proves resume tolerates an auto-load timeout, no cap π―
β¨ SYNOPSIS β¨
void dm_test_dmub_hw_resume_auto_load_timeout (struct kunit *test );
π ARGUMENTS π
testβ the KUnit test context, aka the little group-chat the test lives in π¬
π¦ DESCRIPTION π¦
okay so picture this: the DMUB comes back and reports that the hardware is already initialized, but the firmware literally never signals ready. awkward π The auto-load wait inside resume times out β and the only thing it does is warn.
The whole point of this test: the call must not crash. That's it, that's the vibe. It warns and keeps it moving, periodt. π
π SEE ALSO π
Kernel file
./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_dmub_test.c
and the whole friend group of related tests, all (9), all iconic β¨
dm_test_register_dmub_notify_callback_null_callback(9)dm_test_register_dmub_notify_callback_type_out_of_range(9)dm_test_register_dmub_notify_callback_valid(9)dm_test_register_dmub_notify_callback_offload_false(9)dm_test_dmub_aux_setconfig_callback_copies_and_completes(9)dm_test_dmub_aux_setconfig_callback_non_aux_no_complete(9)dm_test_dmub_aux_setconfig_callback_aux_with_null_dm_notify(9)dm_test_dmub_aux_setconfig_callback_set_config_reply(9)dm_test_dmub_aux_fused_io_callback_copies_reply_and_completes(9)dm_test_dmub_aux_fused_io_callback_max_ddc_line(9)dm_test_dmub_aux_fused_io_callback_null_args(9)dm_test_get_default_ips_mode_dcn35(9)dm_test_get_default_ips_mode_dcn351(9)dm_test_get_default_ips_mode_dcn36(9)dm_test_get_default_ips_mode_older_than_dcn35(9)dm_test_get_default_ips_mode_newer_default(9)dm_test_dmub_hw_init_no_dmub_srv(9)dm_test_dmub_hw_init_no_fb_info(9)dm_test_dmub_hw_init_no_firmware(9)dm_test_dmub_hw_init_success_fake_dmub(9)dm_test_dmub_hw_init_no_hw_support(9)dm_test_dmub_hw_init_bss_data(9)dm_test_dmub_hw_init_hw_init_fails(9)dm_test_dmub_hw_init_auto_load_timeout(9)dm_test_dmub_hw_init_apu_dpia_dcn35(9)dm_test_dmub_hw_init_sanity_checks_dcn31(9)dm_test_dmub_hw_init_sanity_checks_dcn314(9)dm_test_dmub_hw_init_dmcu_abm(9)dm_test_dmub_hw_resume_no_dmub_srv(9)dm_test_dmub_hw_resume_initialized_dmub(9)dm_test_dmub_hw_resume_full_init(9)dm_test_dmub_hw_resume_init_check_failed(9)dm_test_dmub_sw_init_unsupported_asic(9)dm_test_init_microcode_unsupported_asic(9)dm_test_dmub_get_vbios_bounding_box_default_null(9)dm_test_execute_dmub_cmd_null_dmub_srv(9)dm_test_process_dmub_aux_transfer_sync_engine_acquire(9)dm_test_process_dmub_aux_transfer_sync_protocol_error(9)dm_test_process_dmub_aux_transfer_sync_copies_data(9)dm_test_process_dmub_aux_transfer_sync_zero_length(9)dm_test_process_dmub_set_config_sync_unknown_error(9)dm_test_abort_fused_io_no_dmub_srv(9)
that's the whole page, bestie β go forth and test with main character energy π
sign-off szn π: this one comes from ./drivers/gpu/drm/amd/display/... and it's dated October 2026 β yes, future-dated, we love a forward-thinking queen β¨π
π¦ 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