zl3073x_prop...ge_label_set(9)

💅 zl3073x_prop...ge_label_set(9)

okay so this is a page from the Kernel API Manual bestie, and the function name got a little truncated in the header (zl3073x_prop...ge_label_set(9)) but like, we move, the full name is right below 👇

---

✨ NAME ✨

zl3073x_prop_pin_package_label_set — get package label for the pin 🎀

(yes bestie the description says "get" even though the function says "set", that's literally what the original says and I'm not about to gaslight you, we report and we do not editorialize 💀)

---

🦋 SYNOPSIS 🦋

void zl3073x_prop_pin_package_label_set (struct zl3073x_dev *zldev ,
struct zl3073x_pin_props *props , enum dpll_pin_direction dir , u8 id );

no return value, it's giving void — it just does the thing and dips 😌

---

🌸 ARGUMENTS 🌸

• zldev — pointer to zl3073x device 👑 the main character struct
• props — pointer to pin properties ✨ the place stuff gets stored
• dir — pin direction 🧭 which way the pin is facing
• id — pin index 🔢 which pin we're talking about, numbered

---

💖 DESCRIPTION 💖

So what it does: it generates a package label string and stores it right into the pin properties structure. That's it, that's the whole vibe 🫶

Here are the possible formats, and I need you to keep these EXACT ngl:

• REF<n> — differential input reference 🔥
• REF<n>P & REF<n>N — single-ended input reference (P or N pin) 🌈
• OUT<n> — differential output ⭐
• OUT<n>P & OUT<n>N — single-ended output (P or N pin) 💜

so like, <n> is the number, P/N is which pin of the pair, and the REF vs OUT tells you input vs output. iconic honestly 💅

---

🎀 SEE ALSO 🎀

Kernel file ./drivers/dpll/zl3073x/prop.c — go read it bestie, it's right there 📖

• zl3073x_pin_check_freq(9)
• zl3073x_prop_pin_fwnode_get(9)
• zl3073x_pin_props_get(9)
• zl3073x_pin_props_put(9)
• zl3073x_prop_dpll_type_get(9)

---

mwah 💋 that's the whole page. sourced from ./drivers/dpll/zl3073x, dated October 2026 — yes the future, don't ask, slay 🦋✨