dm_mst_test_...on_ack_reply(9)
π dm_mst_test_aux_transfer_non_ack_reply(9) β or, the Kernel API Manual page your bestie has been waiting for π
okay so this is a page straight out of the Kernel API Manual, and it's about one very specific little KUnit test. it's giving "hyper-specific unit test that knows exactly what it is." let's get into it β¨
πΈ NAME πΈ
dm_mst_test_aux_transfer_non_ack_reply β bestie, the whole vibe is: a non-ACK AUX reply gets logged. that's it. that's the function. π
π¦ SYNOPSIS π¦
void dm_mst_test_aux_transfer_non_ack_reply (struct kunit *test );
yep, that's the whole signature. void return, one arg, no cap. (yes there's a space before the closing paren in the original and we're keeping it, character for character, don't come for me π)
β¨ ARGUMENTS β¨
testβ the KUnit test context. that's the whole thing. it's the little handle the test framework passes in so the test can do its thing. π«Ά
π DESCRIPTION π
so here's what's happening, and honestly it's lowkey iconic: when you do a successful read and the reply byte is nonzero, the test wants to make sure the call still returns the backend byte count β while it's exercising the path that handles a non-ACK reply. π₯
like, two things at once. it ate. periodt.
ngl the point of this test is exactly that combo β nonzero reply byte, still successful read, correct byte count, and the non-ACK reply handling path gets its moment in the spotlight. β
π SEE ALSO π
okay buckle up bestie, this list is a whole friend group and we're naming every single one of them, no skipping π
Kernel file:
./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_mst_types_test.c
and the rest of the squad:
dm_mst_test_needs_dsc_aux_workaround_match(9)dm_mst_test_needs_dsc_aux_workaround_rev12(9)dm_mst_test_needs_dsc_aux_workaround_wrong_dev_id(9)dm_mst_test_needs_dsc_aux_workaround_wrong_rev(9)dm_mst_test_needs_dsc_aux_workaround_low_sink_count(9)dm_mst_test_needs_dsc_aux_workaround_zero_sink_count(9)dm_mst_test_pbn_divider_null_link(9)dm_mst_test_pbn_divider_uses_link_bandwidth(9)dm_mst_test_reset_connector_setting(9)dm_mst_test_retrieve_downstream_no_aux(9)dm_mst_test_retrieve_downstream_present(9)dm_mst_test_retrieve_downstream_aux_error(9)dm_mst_test_retrieve_branch_no_parent(9)dm_mst_test_retrieve_branch_reads_oui(9)dm_mst_test_aux_result_success(9)dm_mst_test_aux_result_eio(9)dm_mst_test_aux_result_ebusy(9)dm_mst_test_aux_result_timeout(9)dm_mst_test_aux_transfer_native_read(9)dm_mst_test_aux_transfer_native_write(9)dm_mst_test_aux_transfer_partial_write(9)dm_mst_test_aux_transfer_error_result(9)dm_mst_test_aux_transfer_hpd_discon_quirk(9)dm_mst_test_fill_payload_flags_native_write(9)dm_mst_test_fill_payload_flags_native_read(9)dm_mst_test_fill_payload_flags_i2c_read_mot(9)dm_mst_test_fill_payload_flags_write_status(9)dm_mst_test_msg_ready_mask(9)dm_mst_test_select_esi_dpcd_legacy(9)dm_mst_test_select_esi_dpcd_esi(9)dm_mst_test_sideband_msg_ready_no_ready_bits(9)dm_mst_test_sideband_msg_ready_read_error(9)dm_mst_test_sideband_msg_ready_without_mst_state(9)dm_mst_test_down_rep_msg_ready_wrapper(9)dm_mst_test_initialize_dp_connector_edp(9)dm_mst_test_initialize_dp_connector_mst(9)dm_mst_test_atomic_best_encoder(9)dm_mst_test_create_fake_mst_encoders(9)dm_mst_test_atomic_check_no_old_crtc(9)dm_mst_test_detect_unregistered(9)dm_mst_test_fp_guarded_public_stubs(9)
like I said. huge friend group. everyone showed up to the function-call party π
and that's the whole page!! mwah π
cute little sign-off: this one lives under ./drivers/gpu/drm/amd/display/..., it's dated October 2026, and it answers to the name dm_mst_test_...on_ack_reply(9). go read the other tests bestie, they're all listed above and they're all waiting for you ππ§ββοΈ
π¦ 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