qmi_encode_string_elem(9)

📦 version 7.3.1, in nixpkgs unstable

💖 qmi_encode_string_elem(9) 💖

okay so bestie, welcome to the Kernel API Manual entry for qmi_encode_string_elem — yes that's the function, and yes it's a whole vibe. sit down, grab a strawberry, we're encoding strings ✨

🌸 NAME 🌸

qmi_encode_string_elem — the girly that encodes elements of string data type 🎀

🦋 SYNOPSIS 🦋

int qmi_encode_string_elem (const struct qmi_elem_info *ei_array , void
*buf_dst , const void *buf_src , u32 out_buf_len , int enc_level );

like literally that's the whole signature, no cap. five args, one int coming back at you 💅

👑 ARGUMENTS 👑

  • ei_array — the struct info array that's out here describing the string element. it's giving "I know what this string is" energy 🫶
  • buf_dst — the buffer where the encoded info goes to live its best life. destination era.
  • buf_src — the buffer holding the elements we're about to encode. source era. main character.
  • out_buf_len — how much space you actually have in the encode buffer. the budget, bestie. respect the budget 😭
  • enc_level — how deep this string element sits from the main structure. depth check! 🌀

✨ DESCRIPTION ✨

so what this function does: it encodes a string element — max length ei_array->elem_len bytes, that's the limit fr fr — pulling it from the source buffer buf_src, and then it stores all that encoded goodness into the destination buffer buf_dst. 🌈

and the slay part? it returns the number of bytes of encoded information. that's it, that's the whole personality 🔥

💜 RETURN 💜

  • the number of bytes of encoded information on success 🎉
  • or a negative errno on error 💀 (not the vibe, but it happens)

🎀 SEE ALSO 🎀

kernel file ./drivers/soc/qcom/qmi_encdec.c — go read it, iykyk 📖 and also these icons:

ok that's the whole page bestie, go forth and encode responsibly 🧚‍♀️

sign-off time: this one came from ./drivers/soc/qcom, dated October 2026, and it's qmi_encode_string_elem(9) forever and always 💖 mwah 💋

📦 where this page comes from