tb_cfg_reset(9)

🌸 NAME 🌸

tb_cfg_reset — send a reset packet and wait for a response. This is the Kernel API Manual entry, and yes bestie, we’re getting into it 💅.

✨ SYNOPSIS ✨

struct tb_cfg_result tb_cfg_reset (struct tb_ctl *ctl , u64 route );

🎀 ARGUMENTS 🎀

• ctl — Control channel pointer. That’s the plug, basically 🔌
• route — Router string for the router to send reset. Tell it where to go, bestie 🫶

💅 DESCRIPTION 💅

okay so here’s the tea: if the switch at route is incorrectly configured then we will not receive a reply (even though the switch will reset). The caller should check for -ETIMEDOUT and attempt to reconfigure the switch.

🚨 lowkey important: that ghosting-by-switch situation is exactly why you check -ETIMEDOUT and try reconfiguring — no cap.

🦋 RETURN 🦋

You get a struct tb_cfg_result with a non-zero err field if error has occurred. That’s the whole return vibe.

🌈 SEE ALSO 🌈

Kernel file ./drivers/thunderbolt/ctl.c, struct tb_ctl(9), tb_cfg_request_alloc(9), tb_cfg_request_get(9), tb_cfg_request_put(9), tb_cfg_request(9), tb_cfg_request_cancel(9), tb_cfg_request_sync(9), tb_ctl_alloc(9), tb_ctl_free(9), tb_ctl_start(9), tb_ctl_stop(9), tb_cfg_ack_notification(9), tb_cfg_ack_plug(9), tb_cfg_read_raw(9), tb_cfg_write_raw(9), tb_cfg_get_upstream_port(9) — go read these next, bestie 🫶.

xoxo, your Kernel API Manual bestie 💖 — footer vibes: source/version path ./drivers/thunderbolt, date October 2026, and this icon is tb_cfg_reset(9). periodt 💅