pch_phub_rea...fy_write_reg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ pch_phub_read_modify_write_reg ✨

okay so this is a page from the Kernel API Manual bestie, and the function has the longest name ever β€” pch_phub_read_modify_write_reg πŸ’… β€” the header truncated it to pch_phub_rea...fy_write_reg(9) but we're gonna say the whole thing, obviously.


🌸 NAME 🌸

pch_phub_read_modify_write_reg β€” reading, modifying, and writing a register. yes, all three. it's giving "do everything" energy πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

void pch_phub_read_modify_write_reg (struct pch_phub_reg *chip ,
unsigned int reg_addr_offset , unsigned int data , unsigned int mask );

like, it returns void, so don't go looking for a return value, there isn't one πŸŽ€


πŸ’– ARGUMENTS πŸ’–

  • chip β€” a pointer to the struct pch_phub_reg structure. that's your PHUB register struct bestie, hold it gently 🫢
  • reg_addr_offset β€” the register offset address value. literally the address offset. of the register. iykyk ✨
  • data β€” the writing value. this is the thing you're writing, no cap πŸ’«
  • mask β€” the mask value. it's a mask. it masks πŸ”₯

🌈 SEE ALSO 🌈

the whole PHUB friend group fr fr, go read them all πŸ’œ


ngl this one's short and sweet β€” no environment variables, no exit statuses, no warnings to scream about. just vibes and a register getting read-modified-written 🌸

and that's the whole page!! sourced from ./drivers/misc, dated October 2026, per the pch_phub_rea...fy_write_reg(9) footer. mwah, go forth and modify some registers πŸ’…πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from