pch_phub_rea...fy_write_reg(9)
β¨ 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 thestruct pch_phub_regstructure. 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 π
- Kernel file
./drivers/misc/pch_phub.cβ and alsostruct pch_phub_reg(9)π pch_phub_read_serial_rom(9)pch_phub_write_serial_rom(9)pch_phub_read_serial_rom_val(9)pch_phub_write_serial_rom_val(9)pch_phub_read_gbe_mac_addr(9)pch_phub_write_gbe_mac_addr(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms