tps65090_re...current_wait(9)
π tps65090_re...current_wait(9) π
okay so bestie, welcome to the Kernel API Manual β yes, that's the manual name, we're in the kernel docs now, put your hair up π this one's a little regulator function and honestly? it's giving "small but important."
β¨ NAME β¨
tps65090_reg_set_overcurrent_wait β Setup overcurrent wait π«Ά
That's literally the whole vibe. It sets up the overcurrent wait. Slay.
πΈ SYNOPSIS πΈ
int tps65090_reg_set_overcurrent_wait (struct tps65090_regulator *ri ,
struct regulator_dev *rdev );
no cap, that's the exact signature, character for character, don't come for me π
π¦ ARGUMENTS π¦
riβ Overall regulator data π the big-picture regulator info, the main character of this call nglrdevβ Regulator device β¨ the actual regulator device we're working with
π§ DESCRIPTION π§
so here's the tea π β this function sets the overcurrent wait time based on what's in the regulator info. that's it, that's the plot. it literally just reads what ri is holding and sets the overcurrent wait accordingly. obsessed with a function that knows exactly what it's about tbh π
π RETURN π
0β no error, we ate, everything's fine π- non-zero β there was an error writing the register π so like, the register write didn't go through, and that's your signal
fr fr, don't ignore a non-zero return here β that means the register write was a flop π
π₯ SEE ALSO π₯
- Kernel file
./drivers/regulator/tps65090-regulator.c struct tps65090_regulator(9)tps65090_try_enable_fet(9)tps65090_fet_enable(9)
iykyk, go read those next, they're all connected π§ββοΈβ¨
and that's the page bestie π sign-off time: this came from the manpage source in ./drivers/regulator, dated October 2026, and the header/footer both say tps65090_re...current_wait(9) β yes the truncation is real, it's iconic, we don't fix it π
periodt π
π¦ 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