i2c_client_get_device_id(9)

💖 i2c_client_get_device_id 💖

okay so bestie, welcome to the Kernel API Manual entry for i2c_client_get_device_id — yes the whole function name is the title, she said main character energy only 🎀

---

✨ NAME ✨

i2c_client_get_device_id — get the driver match table entry of a device 🦋

---

🌸 SYNOPSIS 🌸

const struct i2c_device_id * i2c_client_get_device_id (const struct
i2c_client *client );

like literally that's the whole signature, no cap 💅

---

🎀 ARGUMENTS 🎀

• client — the device to query. and listen, the device must be bound to a driver, ok? that's not a vibe suggestion, that's a requirement 🙈

---

💜 DESCRIPTION 💜

Returns a pointer to the matching entry if found — and NULL otherwise. that's it, that's the whole plot 🍓

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/i2c/i2c-core-base.c — go read her, she's iconic 👑

• 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_unregister_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_get_dma_safe_msg_buf(9)
• i2c_put_dma_safe_msg_buf(9)

---

and that's the whole page, bestie!! slay 💖 this one lives in ./drivers/i2c, dated October 2026 — mwah, see u in the next manpage ✨🫶