dm_test_dmu...u_dpia_dcn35(9)
π dm_test_dmub_hw_init_apu_dpia_dcn35 β from the Kernel API Manual, bestie β¨
okay so like. this whole page lives in the Kernel API Manual and honestly it's serving serious "niche but iconic" energy π
πΈ NAME πΈ
dm_test_dmub_hw_init_apu_dpia_dcn35 β the test that checks hw init on APU DPIA and the DCN35 hw params, no cap π
π¦ SYNOPSIS π¦
void dm_test_dmub_hw_init_apu_dpia_dcn35 (struct kunit *test );
β¨ ARGUMENTS β¨
testβ literally just the KUnit test context, that's it, that's the whole argument π«Ά
π DESCRIPTION π
so picture this: you're on a DCN3.5 APU with a USB4 DPIA link, right? dm_dmub_hw_init is supposed to do its little thing and populate the DPIA hw params and the DCN3.5 IPS-sequential hw params β and it has to do all of that before it initializes the fake DMUB service. order matters, bestie, the vibe check is real ππ₯
π SEE ALSO π
π The source file
./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_dmub_test.c
β The whole squad (yes, all of them, I'm not skipping anyone π)
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_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_hw_resume_auto_load_timeout(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)
ngl there is genuinely nothing scary on this page π no dangerous flags, no deprecated anything, no wild exit codes β it's just a KUnit test doing its lil hw-init homework. slay.
mwah π that's the whole page β sourced from ./drivers/gpu/drm/amd/display/... and stamped October 2026, so mark your calendars bestie, this one's dated and iconic πβ¨
π¦ 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