i2c_unregister_device(9)

✨ i2c_unregister_device ✨

okay so bestie, welcome to the Kernel API Manual page for i2c_unregister_device — yes, the one with the (9) after it, that's the section number, we love a formal queen 💅

🌸 NAME 🌸

i2c_unregister_device — literally the reverse effect of i2c_new_*_device(), no cap 🫶

🦋 SYNOPSIS 🦋

void i2c_unregister_device (struct i2c_client *client );

it returns void, so like… nothing comes back. she just does the thing and leaves. main character energy honestly 👑

🎀 ARGUMENTS 🎀

• client — the value you got back from i2c_new_*_device. like, the exact same pointer, don't get cute and pass something else 🙈

⭐ CONTEXT ⭐

can sleep 😴 — yes she can sleep, which means you're allowed to call her from a context where sleeping is legal. she is NOT an atomic-context girlie, so please don't put her in an interrupt handler, i'm begging 😭

💖 SEE ALSO 💖

the whole friend group, fr fr — kernel file ./drivers/i2c/i2c-core-base.c and all her besties:

• i2c_verify_client(9)
• i2c_adapter_lock_bus(9)
• i2c_adapter_trylock_bus(9)
• i2c_adapter_unlock_bus(9)
• i2c_new_client_device(9)
• i2c_find_device_by_fwnode(9)
• i2c_new_dummy_device(9)
• devm_i2c_new_dummy_device(9)
• i2c_new_ancillary_device(9)
• i2c_verify_adapter(9)
• i2c_handle_smbus_host_notify(9)
• i2c_add_adapter(9)
• i2c_add_numbered_adapter(9)
• i2c_del_adapter(9)
• devm_i2c_add_adapter(9)
• i2c_find_adapter_by_fwnode(9)
• i2c_get_adapter_by_fwnode(9)
• i2c_parse_fw_timings(9)
• i2c_del_driver(9)
• __i2c_transfer(9)
• i2c_transfer(9)
• i2c_transfer_buffer_flags(9)
• i2c_get_device_id(9)
• i2c_client_get_device_id(9)
• i2c_get_dma_safe_msg_buf(9)
• i2c_put_dma_safe_msg_buf(9)

and that's the whole page, mwah 💋 this came from the source tree at ./drivers/i2c, dated October 2026, and it's filed under i2c_unregister_device(9) — ily, go free your clients responsibly 🧚‍♀️🌷✨