STRUCT DMUB_SRV_REGION_PARAMS(9)
πΈ struct dmub_srv_region_params(9) πΈ
okay so bestie, welcome to the Kernel API Manual β yes that Kernel API Manual, the one with all the DRM/AMD display lore β and today's main character is struct dmub_srv_region_params. it's giving "little struct, big job" energy ngl π
β¨ NAME β¨
struct dmub_srv_region_params β the params used for calculating dmub regions π
π¦ SYNOPSIS π¦
okay so here's the whole vibe, laid out exactly:
struct dmub_srv_region_params {
uint32_t inst_const_size;
uint32_t bss_data_size;
uint32_t vbios_size;
const uint8_t *fw_inst_const;
const uint8_t *fw_bss_data;
const enum dmub_window_memory_type *window_memory_type;
const struct dmub_fw_meta_info *fw_info;
};
like, that's the struct. that's her. she's iconic and she's holding a lot of uint32_ts and const pointers π«Ά
π Members π
so the manual only spills the tea on four of these fields β the rest are just sitting there looking pretty, iykyk π but here's what we do know:
inst_const_sizeβ the size of the fw inst const section, literally that's it, that's the whole vibe β¨bss_data_sizeβ the size of the fw bss data section, same energy, different section π«vbios_sizeβ the size of the vbios data π₯fw_bss_dataβ the raw firmware bss data section, no cap, it's aconst uint8_t *and it's just raw bytes out here living its truth π
lowkey note bestie: the synopsis shows the full struct, but only these four members get a write-up here. the others are real, they're just not documented on this page, so don't come for me π
π SEE ALSO π
okay this list is long long, but every single one of them ate, so here we go, no skipping, we're being thorough bestie π
- Kernel file
./drivers/gpu/drm/amd/display/dmub/dmub_srv.hDMUB interface and operation(9) struct dmub_region(9)struct dmub_window(9)struct dmub_fb(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_update_inbox_status(9)dmub_srv_get_preos_info(9)dmub_srv_get_fw_meta_info_from_raw_fw(9)
likeβ¦ forty-something cross-references?? she's connected, she knows everybody, main character energy fr fr π
and that's the page bestie!! this one came from ./drivers/gpu/drm/amd/display/... and it's dated October 2026, printed up all nice as struct dmub_srv_region_params(9) β go forth and calculate those regions, you've got this πβ¨π
π¦ 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