STRUCT IMAGE_INFO(9)

💖 struct image_info(9) 💖

okay bestie, so we're in Kernel API Manual territory today and the star of the show is struct image_info — literally just "Firmware and RDDM table" and nothing more, and honestly? iconic minimalism. ✨

---

🌸 SYNOPSIS 🌸

like, here's the whole vibe, exactly as written, no notes:

struct image_info {
    u32 entries;
    struct mhi_buf mhi_buf[];
};

that's it. that's the struct. the way it's so small but carries so much responsibility? main character energy fr fr. 👑

---

🎀 Members 🎀

• entries — the # of entries in table. yes, the manpage really does just say "# of entries in table" and we're respecting it. it's giving "confident, doesn't overexplain." 💅
• mhi_buf — Buffer for firmware and RDDM table. that's the payload zone, the whole reason this struct exists, the moment. 🦋

ngl there are exactly two members and both of them are doing their job. no cap.

---

🌈 SEE ALSO 🌈

okay this is the part where the manpage goes absolutely feral with cross-references, and i'm obsessed. every single one, in order, no skips, because we do not leave the girlies behind:

the enums and structs (the whole family):

• enum mhi_callback(9)
• enum mhi_flags(9)
• enum mhi_device_type(9)
• enum mhi_ch_type(9)
• struct mhi_buf(9)
• struct mhi_link_info(9)
• enum mhi_ee_type(9)
• enum mhi_state(9)
• enum mhi_ch_ee_mask(9)
• enum mhi_er_data_type(9)
• enum mhi_db_brst_mode(9)
• struct mhi_channel_config(9)
• struct mhi_event_config(9)
• struct mhi_controller_config(9)
• struct mhi_controller(9)
• struct mhi_device(9)
• struct mhi_result(9)
• struct mhi_driver(9)

the controller lifecycle (setup to teardown, a whole journey):

• mhi_alloc_controller(9)
• mhi_free_controller(9)
• mhi_register_controller(9)
• mhi_unregister_controller(9)
• __mhi_driver_register(9)
• mhi_driver_unregister(9)
• mhi_set_mhi_state(9)
• mhi_notify(9)
• mhi_get_free_desc_count(9)

power stuff (the dramatic chapters):

• mhi_prepare_for_power_up(9)
• mhi_async_power_up(9)
• mhi_sync_power_up(9)
• mhi_power_down(9)
• mhi_power_down_keep_dev(9)
• mhi_unprepare_after_power_down(9)
• mhi_pm_suspend(9)
• mhi_pm_resume(9)
• mhi_pm_resume_force(9)

RDDM mode (the deep lore 🌀):

• mhi_download_rddm_image(9)
• mhi_force_rddm_mode(9)

asking the device how it's doing:

• mhi_get_exec_env(9)
• mhi_get_mhi_state(9)
• mhi_soc_reset(9)

device refcount + transfers (the day-to-day):

• mhi_device_get_sync(9)
• mhi_device_put(9)
• mhi_prepare_for_transfer(9)
• mhi_unprepare_from_transfer(9)

queueing (where the buffers actually go):

• mhi_queue_buf(9)
• mhi_queue_skb(9)
• mhi_queue_is_full(9)
• mhi_get_channel_doorbell_offset(9)

💀 that's 49 references and yes, i counted, and yes, __mhi_driver_register(9) keeps its double underscore exactly how it is, don't touch her.

---

🫶 the kernel file drop 🫶

this page lives in the kernel tree at:

./include/linux

so if you ever need to find it irl, iykyk. 🧚

---

⭐ cute little sign-off ⭐

this blessed page is from Kernel API Manual, dated October 2026, sourced from ./include/linux, and it answers to struct image_info(9) — remember the section number, bestie, section 9 is where all the kernel API girlies hang out. 💜

go forth and reference responsibly. slay. 💅✨🍓