i2c_smbus_read_byte_data(9)
β¨ i2c_smbus_read_byte_data β¨
okay bestie, this one's from the Kernel API Manual, section 9 β pull up a chair π«Ά
πΈ NAME πΈ
i2c_smbus_read_byte_data β the SMBus "read byte" protocol, and honestly? it's giving minimal icon energy π
π¦ SYNOPSIS π¦
s32 i2c_smbus_read_byte_data (const struct i2c_client *client , u8
command );
like, that's the whole vibe. two args, one function, zero drama β¨
π ARGUMENTS π
clientβ handle to the slave device π this is your little connection to the thing you're talking tocommandβ a byte that gets interpreted by the slave, iykyk π₯ the device decides what it means
π DESCRIPTION π
so what does it do? it executes the SMBus "read byte" protocol. that's it, that's the whole thing π
it returns a negative errno β or, if you're lucky and everything slayed, a data byte received from the device π«
no cap: if it comes back negative, that's an error, not a value. do not confuse them bestie π
π SEE ALSO π
the kernel file lives at ./drivers/i2c/i2c-core-smbus.c β and here's the whole friend group π§:
i2c_smbus_pec(9)i2c_smbus_read_byte(9)i2c_smbus_write_byte(9)i2c_smbus_write_byte_data(9)i2c_smbus_read_word_data(9)i2c_smbus_write_word_data(9)i2c_smbus_read_block_data(9)i2c_smbus_write_block_data(9)i2c_smbus_xfer(9)i2c_smbus_read_i2c_block_data_or_emulated(9)i2c_new_smbus_alert_device(9)
okay that's the page!! source path ./drivers/i2c, dated October 2026, manual section 9 β mwah, go read some bytes bestie ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms