devm_hte_register_chip(9)

✨ devm_hte_register_chip — the kernel API manual, bestie edition 💅

Okay so this one is from the Kernel API Manual (devm_hte_register_chip(9)), and it's literally the ✨resource-managed✨ way to get your HTE chip registered. Buckle up, it's short but it's iconic.

---

🌸 NAME 🌸

devm_hte_register_chip — the resource managed API that registers an HTE chip. 🎀

✨ SYNOPSIS ✨

int devm_hte_register_chip (struct hte_chip *chip );

🫶 ARGUMENTS 🫶

• chip — the HTE chip you're adding to the subsystem. That's your main character right there 👑

💖 DESCRIPTION 💖

So here's the vibe: this is what a provider calls to register itself with the HTE subsystem. And the best part? The unregistration is handled automatically when the provider exits. No manual cleanup arc, no messy goodbye episode — the devm machinery does it for you. Slay. 🌈

🔥 RETURN 🔥

• 0 on success 🎉
• a negative error code on failure 😭

🦋 SEE ALSO 🦋

Kernel file ./drivers/hte/hte.c, plus the whole friend group:

• struct hte_ts_info(9)
• struct hte_device(9)
• hte_ts_put(9)
• hte_disable_ts(9)
• hte_enable_ts(9)
• of_hte_req_count(9)
• hte_ts_get(9)
• hte_request_ts_ns(9)
• devm_hte_request_ts_ns(9)
• hte_init_line_attr(9)
• hte_get_clk_src_info(9)
• hte_push_ts_ns(9)

---

ngl if you're writing a provider, this is your girl — register, forget about it, let devm handle the breakup 💀

---

That's the whole page, bestie — filed under ./drivers/hte in the Kernel API Manual, dated October 2026, and yes the footer says devm_hte_register_chip(9) too because the page knows its own name 🧚💜 periodt.