i2c_trylock_bus(9)

💅 i2c_trylock_bus(9) — bestie, this is from the Kernel API Manual

Okay so picture this: you're deep in the kernel, you've got an I2C bus segment, and you want exclusive access to it — but like, only if it's free. You are not about to wait around. This is i2c_trylock_bus(9), and it's giving "try before you commit" energy. 🎀

---

✨ SYNOPSIS ✨

int i2c_trylock_bus (struct i2c_adapter *adapter , unsigned int flags );

Two things go in, one int comes out. Simple. Iconic. 🦋

---

🌸 ARGUMENTS 🌸

• adapter — the target I2C bus segment. Like, the actual bus you're trying to claim. Point at it and go 💅
• flags — this is where you pick your vibe:
  • I2C_LOCK_ROOT_ADAPTER tries to lock the root i2c adapter (yes, the whole top-level situation 👑)
  • I2C_LOCK_SEGMENT tries to lock only this branch in the adapter tree 🌿 — very "just this one, not the whole family" of it

---

⭐ RETURN ⭐

Returns true if the I2C bus segment is locked, false otherwise. That's it. No drama, just a yes or a no. 🫶

Heads up bestie: the page says true / false, but the function signature is int — I'm just reporting what the manual says, no cap. 🙈

---

💖 SEE ALSO 💖

The kernel file ./include/linux/i2c.h, plus the whole friend group:

• i2c_master_recv(9)
• i2c_master_recv_dmasafe(9)
• i2c_master_send(9)
• i2c_master_send_dmasafe(9)
• struct i2c_device_identity(9)
• enum i2c_driver_flags(9)
• struct i2c_driver(9)
• struct i2c_client(9)
• struct i2c_board_info(9)
• I2C_BOARD_INFO(9)
• struct i2c_algorithm(9)
• struct i2c_lock_operations(9)
• struct i2c_timings(9)
• struct i2c_bus_recovery_info(9)
• struct i2c_adapter_quirks(9)
• i2c_lock_bus(9)
• i2c_unlock_bus(9)
• i2c_mark_adapter_suspended(9)
• i2c_mark_adapter_resumed(9)
• i2c_check_quirks(9)
• module_i2c_driver(9)
• builtin_i2c_driver(9)

Like, literally the entire I2C cinematic universe. 🌈

---

And that's the whole page, bestie — sourced from ./include/linux, dated October 2026, filed under i2c_trylock_bus(9). Go lock that bus (or don't, it's a try). Periodt. 💜✨