STRUCT MLX90635_DATA(9)
π NAME
struct mlx90635_data β the private data struct for the MLX90635 device, aka the little backstage closet where this temperature sensor keeps all its stuff π
β¨ SYNOPSIS
struct mlx90635_data {
struct i2c_client *client;
struct mutex lock;
struct regmap *regmap;
struct regmap *regmap_ee;
u16 emissivity;
struct regulator *regulator;
int powerstatus;
unsigned long interaction_ts;
};
Bestie, that's the whole vibe right there β eight fields, zero drama, all business π
π«Ά Members
clientβ the I2C client of the device. literally who this sensor is talking to on the bus πΈlockβ an internal mutex, and ngl it's kinda the main character here: a single triggered measurement needs multiple reads, so this lock exists to keep the data consistent. no cap, it's holding everything together π₯regmapβ the regmap of the device registers. your regular, everyday register map β¨regmap_eeβ the regmap of the device EEPROM, which (fun fact) can be cached πemissivityβ the object emissivity, au16from 0 to 1000, where 1000 = 1. yes, that's the scale, she's built different π¦regulatorβ the regulator of the device. power supply energy πpowerstatusβ the current POWER status of the device (yes, it's uppercase in the name and we respect it) πinteraction_tsβ timestamp of the last temperature read, measured in jiffies, and it's used for power management. so basically "when did we last hang out" but for power π
π§ SEE ALSO
- Kernel file
./drivers/iio/temperature/mlx90635.c mlx90635_reset_delay(9),mlx90635_pm_interaction_wakeup(9)
okay that's the whole page, slay π
it lives over in ./drivers/iio/temperature, dated October 2026, and this was struct mlx90635_data(9) from the Kernel API Manual β go read the source file if you wanna know more, iykyk πβ¨
π¦ 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