tps65217_reg_read(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tps65217_reg_read(9) β€” the Kernel API Manual, bestie edition πŸŽ€

Okay so picture this: you're deep in the kernel, you're in the tps65217 MFD driver, and you just need one single register value. Not a whole block, not a vibe, just one. That's literally this function. It's a section 9 manpage, it lives in the Kernel API Manual, and it's lowkey iconic for how tiny it is. ✨


🌸 NAME 🌸

tps65217_reg_read β€” read a single tps65217 register. That's it. That's the whole job. One register, one read, no drama. 🫢


⭐ SYNOPSIS ⭐

int tps65217_reg_read (struct tps65217 *tps , unsigned int reg ,
       unsigned int *val );

Yep, that's the whole signature. Three args, returns an int. Slay. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • tps β€” the device to read from. Like, the tps65217 you're actually talking to. You gotta tell it which one, bestie, it can't read minds. πŸ™ˆ
  • reg β€” the register to read. Which one? That one. The one you name right here. unsigned int. 🎯
  • val β€” Contians the value. (Yes, that's the original spelling, keeping it exactly as-is, no cap 😭.) This is your unsigned int * β€” a pointer, so the value comes back to you through it. Iconic out-param behaviour. πŸ”₯
Heads up: val is a pointer (unsigned int *val), so whatever you pass in is where the answer lands. Don't pass garbage, please. 🌈

πŸ‘‘ SEE ALSO πŸ‘‘

  • Kernel file ./drivers/mfd/tps65217.c β€” the source itself, go read it, it's giving main character energy 🧚
  • tps65217_reg_write(9) β€” the write counterpart, for when you're feeling destructive ✍️
  • tps65217_update_bits(9) β€” read-modify-write realness, the bits edition πŸ“

And that's the page!! πŸ’– Source: ./drivers/mfd, dated October 2026 β€” go forth and read exactly one register, bestie. Periodt. πŸ’œπŸŒΈπŸ¦‹βœ¨

πŸ“¦ where this page comes from