i2c_dev_get_master(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… i2c_dev_get_master β€” get master used to communicate with a device

Hiii bestie, welcome to the Kernel API Manual entry for i2c_dev_get_master(9) πŸŽ€ β€” yes that's the page number, it's giving "we do things properly here". This one is short and sweet, so let's go ✨


🌸 NAME 🌸

i2c_dev_get_master β€” get master used to communicate with a device

Literally what it says on the tin, no cap. It hands you back the master that's in charge of talking to a given device πŸ’–


✨ SYNOPSIS ✨

struct i3c_master_controller * i2c_dev_get_master (struct i2c_dev_desc
*dev );

Yup, that's the whole signature β€” it returns a pointer to a struct i3c_master_controller, and it takes exactly one thing. Iconic behaviour, honestly πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” I2C dev. That's your device, the one you want the master for. That's it, that's the only argument πŸ“

πŸ’œ RETURN πŸ’œ

the master controller driving dev β€” like, the actual master controller that drives that device. That's the vibe check result and it passed πŸ”₯


🌈 SEE ALSO 🌈

More reading, because we support each other's hyperfixations 🫢 Everything below lives in the Kernel file ./include/linux/i3c/master.h:


Ngl bestie this page is tiny, but that's the whole thing β€” nothing hidden, nothing omitted, every struct and enum accounted for πŸ’€βœ¨

Okay that's the page!! Mwah πŸ’‹ This little drop came from ./include/linux/i3c, landing in October 2026 β€” so go forth, get your masters, and slay πŸ§šβ€β™€οΈπŸ‘‘πŸ’–

πŸ“¦ where this page comes from