bq25703_get_iindpm(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– bq25703_get_iindpm β€” Kernel API Manual ✨

okay bestie, welcome to the function that tells you how much input current your charger is actually letting through. it's a kernel API page (bq25703_get_iindpm(9), if we're being formal πŸ’…) and it's short, sweet, and lowkey iconic. let's go 🫢


✨ NAME ✨

bq25703_get_iindpm β€” get the maximum set input current 🌸


πŸŽ€ SYNOPSIS πŸŽ€

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

like, that's the whole vibe. one struct in, one int pointer out, returns an int 😌


πŸ¦‹ ARGUMENTS πŸ¦‹

  • pdata β€” driver platform data. the whole charger situation, basically. main character energy πŸ’«
  • intval β€” maximum input current value. this is where the answer lands, so don't pass it garbage, fr fr πŸ™ˆ

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea β˜•: this one reads the actual input current limit from the device straight into intval. read it again β€” the actual one, not the one you asked for.

it can differ from the value you programmed, because of some autonomous functions that may be enabled (but bestie, note the parenthetical β€” they are not currently enabled πŸ‘€). that's literally the whole reason there's a different register used for this. different register, different rules, iykyk πŸ’…

ngl it's giving "trust but verify" and honestly? obsessed ✨


πŸ”₯ RETURN πŸ”₯

returns 0 on success πŸ’– or an error if it's unable to read the register value 😭 (yeah, that can happen β€” check your return codes, bestie, always)


🌈 SEE ALSO 🌈

the whole friend group 🫢 β€” every single one of them:

kernel file ./drivers/power/supply/bq257xx_charger.c alongside:


ok that's the page!! go read your registers, hydrate, and remember: intval is a pointer, so pass it something real πŸ“

and finally, the lil sign-off: this beauty lives under ./drivers/power/supply, dated October 2026, and it's filed as bq25703_get_iindpm(9). slay πŸ’…βœ¨

πŸ“¦ where this page comes from