dmub_srv_upd...inbox_status(9)
π dmub_srv_update_inbox_status β the Kernel API Manual moment π
okay bestie, so this page lives in the manual named dmub_srv_upd...inbox_status(9) (yes the title got truncated, it's literally giving "my name is too long for the tab bar" energy, we love her anyway π
). Sit down, hydrate, and let's get into it.
β¨ NAME β¨
dmub_srv_update_inbox_status β updates the pending status for the inbox & reg inbox0. that's it, that's the whole job, and she does it flawlessly π«Ά
πΈ SYNOPSIS πΈ
enum dmub_status dmub_srv_update_inbox_status(struct dmub_srv *dmub);
like... one arg, one return type. clean, minimal, iconic. no cap.
π¦ ARGUMENTS π¦
dmubβ the dmub service β¨ like, the whole service struct. the main character of this function, honestly.
π RETURN π
she comes back with an enum dmub_status and here's the whole vibe check on what each one means:
DMUB_STATUS_OKβ success π everything ate, no crumbs, we move.DMUB_STATUS_TIMEOUTβ the wait for the buffer to flush timed out π like it just... did not flush in time. tragic but valid.DMUB_STATUS_HW_FAILUREβ there's an issue with HW programming π the hardware said "not today."DMUB_STATUS_INVALIDβ unspecified error π the vague mysterious one, our little enigma.
π₯ SEE ALSO π₯
okay this list is LONG, grab a snack, we're going through ALL of it because we don't skip entries in this house π
The kernel file ./drivers/gpu/drm/amd/display/dmub/dmub_srv.h β that's the home turf, go read it, iykyk.
And then the whole friend group:
DMUB interface and operation(9)struct dmub_region(9)struct dmub_window(9)struct dmub_fb(9)struct dmub_srv_region_params(9)struct dmub_srv_fw_meta_info_params(9)struct dmub_srv_region_info(9)struct dmub_srv_memory_params(9)struct dmub_srv_fb_info(9)struct dmub_soc_fb_info(9)struct dmub_diagnostic_data(9)struct dmub_preos_info(9)struct dmub_srv_base_funcs(9)struct dmub_srv_hw_funcs(9)struct dmub_srv_create_params(9)struct dmub_srv(9)struct dmub_notification(9)dmub_srv_create(9)dmub_srv_destroy(9)dmub_srv_calc_region_info(9)dmub_srv_has_hw_support(9)dmub_srv_is_hw_init(9)dmub_srv_hw_init(9)dmub_srv_hw_reset(9)dmub_srv_fb_cmd_queue(9)dmub_srv_fb_cmd_execute(9)dmub_srv_wait_for_hw_pwr_up(9)dmub_srv_wait_for_auto_load(9)dmub_srv_wait_for_phy_init(9)dmub_srv_wait_for_pending(9)dmub_srv_wait_for_idle(9)dmub_srv_send_gpint_command(9)dmub_srv_get_gpint_response(9)dmub_srv_get_gpint_dataout(9)dmub_srv_flush_buffer_mem(9)dmub_srv_get_fw_boot_status(9)dmub_srv_send_inbox0_cmd(9)dmub_srv_wait_for_inbox0_ack(9)dmub_srv_subvp_save_surf_addr(9)dmub_srv_set_power_state(9)dmub_srv_reg_cmd_execute(9)dmub_srv_cmd_get_response(9)dmub_srv_sync_inboxes(9)dmub_srv_wait_for_inbox_free(9)dmub_srv_get_preos_info(9)dmub_srv_get_fw_meta_info_from_raw_fw(9)
like, that's the whole dmub_srv extended universe fr fr. read them all, they're all slay π
π‘ friendly reminder bestie: this page is part of the Linux kernel API docs, so the source path is ./drivers/gpu/drm/amd/display/... and the date on the file is October 2026 β don't come for me, that's just what the footer says π
okay that's the page!! mwah π go call dmub_srv_update_inbox_status, check your dmub pointer isn't null, and have the most slay day ever βππ β with love, your local dmub_srv_upd...inbox_status(9) manual page π§ββοΈ
π¦ 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