scmi_sensor_reading_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ scmi_sensor_reading_get ✨

okay so bestie, this one lives in the Kernel API Manual and ngl it's a whole vibe: you want one sensor number, you get one sensor number. iconic. πŸ’…


🌸 NAME 🌸

scmi_sensor_reading_get β€” literally just read a scalar sensor value πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int scmi_sensor_reading_get (const struct scmi_protocol_handle *ph , u32
sensor_id , u64 *value );

πŸ’– ARGUMENTS πŸ’–

  • ph β€” the protocol handle, your little passport to the SCMI world 🫢
  • sensor_id β€” the sensor ID, like the sensor's @ in the group chat
  • value β€” where the 64bit sensor reading lands; that's the 64bit value sensor reading, bestie ✨

πŸ‘‘ DESCRIPTION πŸ‘‘

so this function hands you back a single 64 bit reading value that represents the sensor value. periodt. πŸ”₯

but here's the tea β˜•: if the platform SCMI Protocol implementation and the sensor support multiple axis and timestamped-reads, this function just returns the first axis while dropping the timestamp value. it's giving "first slide in the carousel" energy, honestly 😭

so if you actually want the full set, use scmi_sensor_reading_get_timestamped instead to retrieve the array of timestamped multi-axis values. that's the main character version, iykyk πŸ’œ


⭐ RETURN ⭐

0 on Success πŸŽ‰


🌈 SEE ALSO 🌈


🫢 friendly reminder: one axis only, timestamp dropped. if that's not the vibe you were going for, go say hi to the timestamped version instead πŸ’…

and that's the whole page, bestie β€” straight from ./drivers/firmware/arm_scmi, October 2026 edition, scmi_sensor_reading_get(9). slay, go read some sensors πŸ§šπŸ’–

πŸ“¦ where this page comes from