ab8500_charg...art_charging(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

ab8500_chargalg_start_charging β€” bestie, it literally starts the charger ✨

So real quick, we're in the Kernel API Manual today, flipping through ab8500_charg...art_charging(9) β€” yes the title got truncated by the terminal, no that's not a typo, that's just how the page header is living its life 😭. Anyway. Charger. Starting. Let's go 🫢


🌸 SYNOPSIS 🌸

void ab8500_chargalg_start_charging (struct ab8500_chargalg *di , int
vset_uv , int iset_ua );

Returns void, meaning it gives you nothing back β€” not a single crumb β€” it just does the thing and dips πŸ’…. Iconic behavior honestly.


πŸŽ€ ARGUMENTS πŸŽ€

  • di β€” pointer to the struct ab8500_chargalg structure. Like, the whole charger-algorithm vibe container. You gotta hand it over 🫴
  • vset_uv β€” the requested charger output voltage, measured in microvolt ⚑
  • iset_ua β€” the requested charger output current, measured in microampere πŸ”‹
Note the units bestie!! microvolt and microampere, not volt and ampere. Do not come in here with your regular-people units, the kernel will simply not know what to do with you πŸ™ˆ

✨ DESCRIPTION ✨

okay so the whole situation here is: a charger is gonna get enabled β€” depending on the requested charger type that was detected previously πŸ‘€. That's the tea. It's not out here guessing, it's not freestyling, it is looking at what was already detected and then enabling accordingly. Detection first, enabling second, that's the order of operations fr fr πŸ¦‹


🌈 SEE ALSO 🌈

Strap in because this list is LONG and honestly kinda iconic πŸ‘‘

Like I said. A whole friend group πŸ§šπŸ’œ Go read them all, iykyk.


okay that's the whole page bestie, you ate that πŸ’…πŸ’– This little gem lives over in ./drivers/power/supply, and the page is dated October 2026 β€” so yeah, future vibes only β­πŸ‘‘ mwah, bye! πŸ“

πŸ“¦ where this page comes from