scmi_sensor..._timestamped(9)

💅 scmi_sensor_reading_get_timestamped(9) — like, the timestamped one

okay so bestie, welcome to the Kernel API Manual ✨ this is the page for scmi_sensor_reading_get_timestamped, and no you're not hallucinating, the name really does have that lil ellipsis situation going on 🎀 (that's scmi_sensor..._timestamped if you're being formal about it). grab a strawberry drink 🍓 and let's get into it.

---

🌸 NAME 🌸

scmi_sensor_reading_get_timestamped — read multiple-axis timestamped values 💫

like, multiple axes, with timestamps. it's giving "I want the whole picture, not just one number" energy fr fr.

---

✨ SYNOPSIS ✨

int scmi_sensor_reading_get_timestamped (const struct
       scmi_protocol_handle *ph , u32 sensor_id , u8 count , struct
       scmi_sensor_reading *readings );

it returns an int (we love a classic), and takes four things: ph, sensor_id, count, readings. all four matter, don't skip any 💅

---

🦋 ARGUMENTS 🦋

• ph — the Protocol handle. your little entry ticket to the SCMI protocol, basically. no handle, no vibes.
• sensor_id — the Sensor ID. which sensor are we talking to? this one. 👑
• count — the length of the provided readings array. i.e. how many slots you're handing over. don't lie to it about the size, that's not the move 🙈
• readings — an array of elements, and each one represents a timestamped per-axis reading of type struct scmi_sensor_reading. so the returned readings come back ordered as the axis descriptors array included in struct scmi_sensor_info ⭐ and the max number of returned elements is min(count, num_axis). ideally your provided array should be of length count equal to num_axis — that's the dream scenario, the "we matched our energies" scenario 🫶

ngl, that min(count, num_axis) is doing real work — if your count is smaller than num_axis, you just get fewer back. it does not overflow your lil array. it's respectful like that. but like… just make count equal to num_axis, bestie. it's the ideal and the manpage says so 😭

---

🔥 RETURN 🔥

• 0 on success. that's it. that's the whole return section. 0 = slay 💀✨

---

💜 SEE ALSO 💜

• the kernel file ./drivers/firmware/arm_scmi/sensors.c — go read the source, it's literally right there 👀
• scmi_sensor_reading_get(9) — the non-timestamped cousin. same family, different energy.

---

okay that's the whole page, no cap 💖 no extra options hiding in the cut, no secret env vars, this one is short and sweet like a good group chat reply 🌈

later bestie 🎀 this page came from ./drivers/firmware/arm_scmi, dated October 2026, and it's living its best life in the Kernel API Manual. periodt. 👑✨