dmub_srv_fb_cmd_queue(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ dmub_srv_fb_cmd_queue(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’… this one's a little kernel-side legend from the DMUB world, and honestly? she's giving "drop it in the queue and let the firmware girlies handle it later" energy πŸŽ€


🌸 NAME 🌸

dmub_srv_fb_cmd_queue β€” queues a command to the DMUB πŸ’Œ


πŸ¦‹ SYNOPSIS πŸ¦‹

enum dmub_status dmub_srv_fb_cmd_queue (struct dmub_srv *dmub , const
union dmub_rb_cmd *cmd );

πŸŽ€ ARGUMENTS πŸŽ€

  • dmub β€” the dmub service 🫢 like, the whole service handle, that's her
  • cmd β€” the command to queue πŸ“¨ the actual message you're sliding into the ring buffer

πŸ’– DESCRIPTION πŸ’–

Queues a command to the DMUB service but does not begin execution immediately. no cap β€” she just puts it in the queue and dips, that's it. it's giving "I sent the text, I'm not waiting for a reply" 😭✨ the execution part is somebody else's main character moment, not hers.


🌈 RETURN 🌈

  • DMUB_STATUS_OK β€” success πŸŽ‰ slay, it went in
  • DMUB_STATUS_QUEUE_FULL β€” no remaining room in queue πŸ’€ like, there is literally no space left, the queue is stuffed
  • DMUB_STATUS_INVALID β€” unspecified error πŸ™ˆ the vibe check failed and nobody will tell you why

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/gpu/drm/amd/display/dmub/dmub_srv.h πŸ—‚οΈ and honestly 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_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_update_inbox_status(9), dmub_srv_get_preos_info(9), dmub_srv_get_fw_meta_info_from_raw_fw(9)

pro tip from your girl: if you ever want the execute era of the timeline, that's dmub_srv_fb_cmd_execute(9) β€” this page is strictly the queue-and-chill part πŸ”₯

okay that's the whole page bestie, you ate that 🫢 the source lives at ./drivers/gpu/drm/amd/display/... and this lil gem is dated October 2026 ⭐ periodt, go queue something πŸ’œβœ¨

πŸ“¦ where this page comes from