STRUCT EC_RESPONSE_READ_TEST(9)

💖 struct ec_response_read_test 💖

okay so bestie, welcome to the Kernel API Manual — yes that's the whole manual name, we're being official today 💅 — and today's main character is a struct. And not just any struct. It's literally the response to the read test command. It's giving "I was called, I answered, here's my data." Iconic behavior, no cap.

---

✨ NAME ✨

struct ec_response_read_test — Response to the read test command.

That's it. That's the vibe. It responds. It tests reads. Slay.

---

🌸 SYNOPSIS 🌸

okay so here's the actual shape of it, and yes you're gonna want to look at this exactly:

struct ec_response_read_test {
    uint32_t data[32];
 };

Lowkey a little cutie. Thirty-two whole uint32_ts of data, just sitting there, waiting to be read. Fr fr it's living its best life.

---

🎀 Members 🎀

• data — Data returned by the read test command. That's the whole personality. It's the payload, it's the moment, it's the data returning from the read test. Periodt. 🫶

ngl bestie, this one's short and sweet — one member, no drama, no hidden gotchas printed here. Just data doing its thing.

---

🦋 SEE ALSO 🦋

okay so this is the part where the manpage goes full group-chat-adds-everyone energy 😭 — but honestly every single one of these is worth knowing, so here's the whole squad, in order, nobody left on read:

• Kernel file ./include/linux/platform_data/cros_ec_commands.h
• struct ec_lpc_host_args(9)
• struct ec_host_request(9)
• struct ec_host_response(9)
• struct ec_response_proto_version(9)
• struct ec_params_hello(9)
• struct ec_response_hello(9)
• struct ec_response_get_version(9)
• struct ec_params_read_test(9)
• struct ec_response_get_chip_info(9)
• struct ec_response_board_version(9)
• struct ec_params_read_memmap(9)
• struct ec_params_get_cmd_versions(9)
• struct ec_params_get_cmd_versions_v1(9)
• struct ec_response_get_cmd_versions(9)
• struct ec_response_get_comms_status(9)
• struct ec_response_get_protocol_info(9)
• struct ec_response_flash_info(9)
• struct ec_response_flash_info_1(9)
• struct ec_params_flash_read(9)
• struct ec_params_flash_write(9)
• struct ec_params_flash_erase(9)
• struct ec_params_flash_erase_v1(9)
• struct ec_params_flash_protect(9)
• struct ec_response_flash_protect(9)
• struct ec_params_flash_region_info(9)
• struct ec_params_flash_select(9)
• struct ec_params_cec_write(9)
• struct ec_params_cec_write_v1(9)
• struct ec_params_cec_read(9)
• struct ec_response_cec_read(9)
• struct ec_params_cec_set(9)
• struct ec_params_cec_get(9)
• struct ec_response_cec_get(9)
• struct ec_response_cec_port_count(9)
• struct ec_params_battery_static_info(9)
• struct ec_response_battery_static_info(9)
• struct ec_params_battery_dynamic_info(9)
• struct ec_response_battery_dynamic_info(9)
• struct ec_params_charger_control(9)

like, the whole family showed up. and yes, struct ec_params_read_test(9) is in there too — that's the request side of this whole situation, so if you're reading this one you probably want its partner in crime too. 👀

---

🌷 and that's the page, bestie! this little gem lives in ./include/linux/platform_data, and it's dated October 2026 — future vibes, we love to see it — with the footer still repping struct ec_re...se_read_test(9) forever and always. drink some water, read your structs, bye 💜✨