qmi_encode_struct_elem(9)

📦 version 7.3.1, in nixpkgs unstable

✨ qmi_encode_struct_elem(9) ✨

okay so bestie, we're in the Kernel API Manual today and the star of the show is qmi_encode_struct_elem — the lil function that encodes elements of struct data type 💅 literally its whole job. no cap.

🎀 SYNOPSIS 🎀

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

like, six args, all business, no filler 💖

🌸 ARGUMENTS 🌸

  • ei_array — the struct info array that describes the struct element. it's giving instruction manual energy 🎀
  • buf_dst — the buffer where the encoded info goes to live. destination era ✨
  • buf_src — the buffer holding the elements you wanna encode. the source, the origin, the main character 👑
  • elem_len — how many elements in buf_src you're encoding, bestie. a count, a number, that's it 🦋
  • out_buf_len — the available space in the encode buffer. respect the limit or perish 💀
  • enc_level — depth of the nested structure from the main structure. how deep in the struct-ception we are 🙈

🦋 DESCRIPTION 🦋

so this function encodes the "elem_len" number of struct elements, and each one is "ei_array->elem_size" bytes big, pulling straight from the source buffer "buf_src", and then it stores the encoded information in the destination buffer "buf_dst". obsessed with the flow honestly ✨

the elements are of struct data type — and lowkey that includes any C structure, so yeah, it's flexible like that 💅

and the return? it hands you back the number of bytes of encoded information. iconic behavior, fr fr 💖

⭐ RETURN ⭐

the number of bytes of encoded information on success 🎉 — or a negative errno on error 😭. so basically, positive = slay, negative = vibe check failed.

🌈 SEE ALSO 🌈

kernel file ./drivers/soc/qcom/qmi_encdec.c and its whole friend group 🫶:

aaaand that's the page!! 🧚 sign-off time: this one comes to you from ./drivers/soc/qcom, dated October 2026, and it's the qmi_encode_struct_elem(9) page — go forth and encode those structs, bestie 💜🍓

📦 where this page comes from