cci_read(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– cci_read(9) β€” like, the CCI register reader bestie πŸ’–

okay so welcome to the Kernel API Manual page for cci_read(9), and honestly? she's a little legend. this is the function you call when you just wanna grab one single value out of one single CCI register. no drama, no fuss, one register, one read. periodt. ✨


🌸 NAME 🌸

cci_read β€” read a value from a single CCI register

like, exactly one. one register. a single little value. she's not doing a whole batch for you, that's a different function's job (see SEE ALSO, iykyk πŸ’…).


πŸ¦‹ SYNOPSIS πŸ¦‹

int cci_read (struct regmap *map , u32 reg , u64 *val , int *err );

look at her. four arguments. iconic behavior. πŸŽ€


✨ ARGUMENTS ✨

  • map β€” the register map you're reading from. this is the vibe check of where the bits live. πŸ—ΊοΈ
  • reg β€” the register address you wanna read. and listen, bestie, use the CCI_REG#() macros to encode the reg width, okay? don't just rawdog the number in there. πŸ™ˆ
  • val β€” pointer to where the read value gets stored. she reads it, she drops it in here. that's the whole deal. πŸ’–
  • err β€” optional pointer for storing errors. and here's the tea: if a previous error is already set, then the read gets skipped entirely. no cap. so if you're passing this in, know that an errored-out err means nothing gets read at all. 🫢

πŸ”₯ RETURN πŸ”₯

0 on success, or a negative error code on failure. that's it, that's the whole return situation. slay. ⭐


πŸ‘‘ SEE ALSO πŸ‘‘

if you're obsessed (and you should be), go check these out too:


πŸ’€ friendly reminder: that err pointer is optional, but if it's already carrying a previous error in it, the read is skipped. so don't be out here expecting a fresh value with a stale error sitting in there. understand the assignment. 🧚

and that's the page!! mwah πŸ’‹ this little writeup lives in ./include/media, dated October 2026, and if you ever forget her name just remember: cci_read(9). bestie behavior from start to finish. πŸŒˆπŸ¦‹πŸ’œ

πŸ“¦ where this page comes from