cros_ec_read_features(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cros_ec_read_features β€” the Kernel API Manual tea β˜•

okay so bestie, you're looking at cros_ec_read_features(9) β€” that's the manual page name and the whole entire vibe of this doc. she lives in the Kernel API Manual and she's about one (1) job: reading them EC features. no cap. πŸ¦‹


✨ NAME ✨

cros_ec_read_features β€” literally just Read EC features. that's it. that's the whole name section. iconic behavior honestly πŸŽ€


🌸 SYNOPSIS 🌸

int cros_ec_read_features (struct cros_ec_dev *ec );

so she takes one friend and she returns an int. simple queen energy πŸ‘‘


πŸ’– ARGUMENTS πŸ’–

  • ec β€” the EC device. that's your bestie right there, the struct cros_ec_dev * you're handing over. she needs it, don't ghost her 🫢

πŸ”₯ RETURN πŸ”₯

  • >= 0 β€” slay!! success!! we ate πŸ’…
  • negative error number β€” not slay 😭 something went wrong, and the number tells you what. read it, don't ignore it, that's the whole point of her.

πŸ¦‹ SEE ALSO πŸ¦‹

okay this is the group chat and everyone's invited, no one gets left on read:

like, go read them. all of them. iykyk 🌈


ngl bestie this whole page is short but she's got range β€” one device pointer in, one status out, and a whole ecosystem of EC functions waiting for you in the SEE ALSO. go be the main character of your own driver 🧚

and that's the whole page, periodt πŸ’€βœ¨

courtesy of the fine folks living in ./drivers/platform/chrome, stamped October 2026, and officially filed under cros_ec_read_features(9). mwah πŸ’‹ πŸ“

πŸ“¦ where this page comes from