hsi_get_channel_id_by_name(9)

✨ NAME ✨

hsi_get_channel_id_by_name — bestie, this is how you acquire a channel id by channel name 💅

(also hi, you're reading a page from the Kernel API Manual, section 9 — welcome to the kernel-API corner of the group chat 🫶)

---

🌸 SYNOPSIS 🌸

int hsi_get_channel_id_by_name (struct hsi_client *cl , char *name );

---

🎀 ARGUMENTS 🎀

• cl — the HSI client, aka the one that's actually gonna use the channel 👑
• name — the name the channel is known under, iykyk 🏷️

---

💖 DESCRIPTION 💖

okay so here's the vibe: clients can call this function to get the hsi channel ids, and it works just like requesting IRQs or GPIOs by name — same energy, different subsystem, no cap ✨

heads up bestie: this function assumes the same channel configuration is used for RX and TX 🔥 like, it's not out here checking both for you, it just assumes. so know that going in 🙈

It returns -errno on error, or the channel id on success 💀➡️👑

---

🦋 SEE ALSO 🦋

Kernel file ./drivers/hsi/hsi_core.c (the main character of this whole story 🌟), plus all these iconic siblings:

• hsi_port_unregister_clients(9)
• hsi_unregister_controller(9)
• hsi_register_controller(9)
• hsi_register_client_driver(9)
• hsi_put_controller(9)
• hsi_alloc_controller(9)
• hsi_free_msg(9)
• hsi_alloc_msg(9)
• hsi_async(9)
• hsi_claim_port(9)
• hsi_release_port(9)
• hsi_register_port_event(9)
• hsi_unregister_port_event(9)
• hsi_event(9)

---

and that's the whole page, bestie 🎀 mwah 💋

source: ./drivers/hsi · dated October 2026 — literally go off, calendar 📅✨ slay 🫶