STRUCT ENTRY_HEADER(9)

🌸 struct entry_header(9) 🌸

okay bestie, welcome to the Kernel API Manual, section 9, where we're gonna talk about struct entry_header — it's literally the header for each entry in cmddb, and yes it's as iconic as it sounds 💅

---

✨ NAME ✨

struct entry_header — the header for each entry in cmddb, no cap 🫶

---

🎀 SYNOPSIS 🎀

like, here's the whole vibe of the struct, verbatim, don't touch a single character:

struct entry_header {
    u8 id[8];
    __le32 priority[NUM_PRIORITY];
    __le32 addr;
    __le16 len;
    __le16 offset;
 };

look at her. she's beautiful. she's little. she's a struct 😭💖

---

👑 MEMBERS 👑

okay so every field is a main character in her own right, let's go through the whole friend group:

• id — the resource's identifier 🆔 like, who is she? this tells you.
• priority — unused 💀 fr fr, nobody's using her right now, she's just kinda here for the vibes. don't come for me, that's literally what the manual says.
• addr — the address of the resource 📍 the actual location, the where, the spot.
• len — length of the data 📏 how much data we're dealing with.
• offset — offset from :data_offset, start of the data 🎯 like, where the data actually kicks off.

ngl the : in :data_offset is literally how it's written in the original, so I'm keeping it exactly. not my typo, bestie, I would never 🙈

---

🦋 SEE ALSO 🦋

go read these next, they're all in the same friend group and they all ate:

• the Kernel file ./drivers/soc/qcom/cmd-db.c ⭐
• struct rsc_hdr(9)
• struct cmd_db_header(9)
• Description of the Command DB database.(9)
• cmd_db_ready(9)
• cmd_db_read_addr(9)
• cmd_db_read_aux_data(9)
• cmd_db_match_resource_addr(9)
• cmd_db_read_slave_id(9)

---

and that's the whole page, bestie!! you understood it, I'm so proud of you 💜

later, bestie — this one lives in ./drivers/soc/qcom, and the page is dated October 2026 ✨🍓 see you in the next manpage, mwah 🎀