find_ei(9)

💅 find_ei(9) 💅

okay bestie, welcome to the Kernel API Manual page for find_ei — it's literally the little helper that finds the element info matching a TLV Type, and we're gonna get into it 💖

✨ NAME ✨

find_ei — find the element info that corresponds to a TLV Type, periodt 💅

🌈 SYNOPSIS 🌈

const struct qmi_elem_info * find_ei (const struct qmi_elem_info
*ei_array , u32 type );

🎀 ARGUMENTS 🎀

• ei_array — the struct info array for the message being decoded ✨
• type — the TLV Type of the element you're searching for 👑

💖 DESCRIPTION 💖

okay so every element that got encoded in the QMI message has a type information associated with it — that's just how it is, no cap 🫶

and while decoding the QMI message, this function is the one you use to find the struct info for the element that corresponds to the type being decoded. it's giving "where is the matching info bestie" energy, and honestly? iconic 💅

⭐ RETURN ⭐

a pointer to the struct info — but only if it's found 👑✨

🦋 SEE ALSO 🦋

• Kernel file ./drivers/soc/qcom/qmi_encdec.c
• skip_to_next_elem(9)
• qmi_calc_min_msg_len(9)
• qmi_encode_basic_elem(9)
• qmi_encode_struct_elem(9)
• qmi_encode_string_elem(9)
• qmi_encode(9)
• qmi_decode_basic_elem(9)
• qmi_decode_struct_elem(9)
• qmi_decode_string_elem(9)
• qmi_decode(9)
• qmi_encode_message(9)
• qmi_decode_message(9)

signing off from the ./drivers/soc/qcom corner, dated October 2026, on the find_ei(9) page — mwah, slay, bye bestie 🫶💖✨