qmi_decode_string_elem(9)

📦 version 7.3.1, in nixpkgs unstable

💅 qmi_decode_string_elem(9) — like, the Kernel API Manual, section 9, bestie 🎀

okay so we're in the Kernel API Manual, section 9, and today's main character is qmi_decode_string_elem ✨

🌸 NAME 🌸

qmi_decode_string_elem — decodes elements of string data type 🧚‍♀️

⭐ SYNOPSIS ⭐

int qmi_decode_string_elem (const struct qmi_elem_info *ei_array , void
*buf_dst , const void *buf_src , u32 tlv_len , int dec_level );

💖 ARGUMENTS 💖

  • ei_array — the struct info array that describes the string element. it's giving "here's the blueprint" 🫶
  • buf_dst — the buffer where the decoded element gets stored. destiny buffer fr fr ✨
  • buf_src — the buffer holding the elements in QMI wire format. the source of truth 💅
  • tlv_len — total size of the encoded info that corresponds to this string element 📏
  • dec_level — how deep the string element sits from the main structure. nesting vibes 🪆

🦋 DESCRIPTION 🦋

okay so this function decodes the string element of maximum length "ei_array->elem_len" from the source buffer "buf_src" and puts it into the destination buffer "buf_dst". no cap. 💫

and then — the moment you've been waiting for — it returns the number of bytes decoded from the input buffer 👑

🔥 RETURN 🔥

on success you get the total size of the decoded data elements ✨ on error it's a negative errno 😭 (we don't love that for us, but the info is there)

🌈 SEE ALSO 🌈

Kernel file ./drivers/soc/qcom/qmi_encdec.c — go read it, iykyk 📖

that's the whole page bestie, every single detail preserved, nothing dropped, we ate and left no crumbs 💅

and that's a wrap!! sourced from ./drivers/soc/qcom, dated October 2026, page qmi_decode_string_elem(9) — mwah, go decode some strings 🍓💜

📦 where this page comes from