STRUCT HSI_BOARD_INFO(9)

💅 struct hsi_board_info(9) — Kernel API Manual

okay bestie, so you're in the Kernel API Manual and this is literally the page for struct hsi_board_info and it's giving "the little index card that tells the kernel where your HSI client lives" energy 🎀

✨ NAME ✨

struct hsi_board_info — HSI client board info 🦋

like, it's the board info. for an HSI client. no cap, that's the whole vibe 🌸

✨ SYNOPSIS ✨

struct hsi_board_info {
    const char              *name;
    unsigned int            hsi_id;
    unsigned int            port;
    struct hsi_config       tx_cfg;
    struct hsi_config       rx_cfg;
    void *platform_data;
    struct dev_archdata     *archdata;
 };

yes queen, copy it exactly like that, character for character, I'm not about to let you typo your way through a struct definition 😭

🌈 Members 🌈

• name — the name for the HSI device 💖 like its little nametag at the group chat
• hsi_id — the HSI controller id where the client sits 🫶 which controller is home
• port — the port number in the controller where the client sits ⭐ which specific door in that home
• tx_cfg — HSI TX configuration 🔥 the transmit settings, periodt
• rx_cfg — HSI RX configuration 🌸 the receive settings, equally iconic
• platform_data — platform related data 🧚 the board-specific extras
• archdata — architecture-dependent device data 💜 the arch's own private business, iykyk

✨ SEE ALSO ✨

so if you wanna keep reading (and you should, you're doing amazing 💅), go check the kernel file ./include/linux/hsi/hsi.h and then these besties:

• struct hsi_channel(9)
• struct hsi_config(9)
• struct hsi_client(9)
• struct hsi_client_driver(9)
• struct hsi_msg(9)
• struct hsi_port(9)
• struct hsi_controller(9)
• hsi_id(9)
• hsi_port_id(9)
• hsi_setup(9)
• hsi_flush(9)
• hsi_async_read(9)
• hsi_async_write(9)
• hsi_start_tx(9)
• hsi_stop_tx(9)

and that's the whole page, bestie 🎀 it's from ./include/linux/hsi, dated October 2026, and it lives under the Kernel API Manual — mwah, go slay your HSI setup 💖✨🦋