cdx_mcdi_get_dev_config(9)

💅 cdx_mcdi_get_dev_config(9) — from the Kernel API Manual

okay bestie, gather round 🫶 this one is a kernel API manual page, and yes it's exactly as niche as it sounds, but we're gonna make it make sense.

✨ NAME ✨

cdx_mcdi_get_dev_config — gets the configuration for a particular bus_num:dev_num 🎀

✨ SYNOPSIS ✨

int cdx_mcdi_get_dev_config (struct cdx_mcdi *cdx , u8 bus_num , u8
dev_num , struct cdx_dev_params *dev_params );

✨ ARGUMENTS ✨

• cdx — pointer to the MCDI interface. literally the main character here 👑
• bus_num — the bus number.
• dev_num — the device number.
• dev_params — pointer to cdx_dev_params, and this is populated by this device with the configuration corresponding to the bus_num:dev_num you provided. so you hand it the pointer, it fills in the tea ☕✨

✨ RETURN ✨

word-for-word, no cap: 0 total number of devices available on the bus, <0 on failure. so yeah — a 0 on success, and anything below zero means it did not slay 😭💀

✨ SEE ALSO ✨

• Kernel file ./drivers/cdx/controller/mcdi_functions.h — go read the source, iykyk 🦋
• cdx_mcdi_get_num_buses(9)
• cdx_mcdi_get_num_devs(9)
• cdx_mcdi_bus_enable(9)
• cdx_mcdi_bus_disable(9)
• cdx_mcdi_write_msi(9)
• cdx_mcdi_reset_device(9)
• cdx_mcdi_bus_master_enable(9)
• cdx_mcdi_msi_enable(9)

and that's the whole page, bestie — no filler, just facts 💖 this one lives at ./drivers/cdx/controller, dated October 2026, and it's giving very much cdx_mcdi_get_dev_config(9) energy. periodt 🌸🎀