bq25792_get_chrg_volt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bq25792_get_chrg_volt(9) β€” like, the Kernel API Manual page you actually wanna read πŸŽ€

okay bestie, welcome to the Kernel API Manual entry for bq25792_get_chrg_volt, and no this is not a drill, we're reading kernel docs together and it's gonna be iconic ✨


🌸 NAME 🌸

bq25792_get_chrg_volt β€” get the maximum set charge voltage πŸ’–

⚑ SYNOPSIS ⚑

int bq25792_get_chrg_volt (struct bq257xx_chg *pdata , int *intval );

🫢 ARGUMENTS 🫢

  • pdata β€” the driver platform data. it's giving "the context object you gotta hand over before anything works" energy πŸ¦‹
  • intval β€” a pointer where the maximum charge voltage value gets stashed. literally, that's where the answer lands. πŸ’…

πŸ”₯ DESCRIPTION πŸ”₯

So the whole vibe of this function? It reads the current charge voltage limit straight off the device. that's it, that's the tea β˜• β€” it goes and fetches the limit that's set rn, no cap.

πŸ‘‘ RETURN πŸ‘‘

Returns 0 on success, or an error if it fumbled reading the value 😭 (i.e. error on failure to read value β€” fr fr, check it).

ngl bestie, always check that return value. the 0 is the slay, anything else is the πŸ’€.

🌈 SEE ALSO 🌈

Kernel file ./drivers/power/supply/bq257xx_charger.c πŸ“ and the whole squad:


and that's the whole page, bestie 🧚 that's a wrap πŸŽ€

source: ./drivers/power/supply Β· dated October 2026 Β· manual page bq25792_get_chrg_volt(9) β€” ty for reading, ily, go check your return codes πŸ’œβœ¨

πŸ“¦ where this page comes from