ab8500_charger_max_usb_curr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ab8500_charger_max_usb_curr πŸ’–

okay so bestie, this is a page from the Kernel API Manual β€” yes, the actual ab8500_charger_max_usb_curr(9) one β€” and it's honestly shorter than my attention span, so we're gonna get through it together. 🫢


✨ NAME ✨

ab8500_charger_max_usb_curr β€” get the max curr for the USB type

like, it literally tells you the ceiling of how much juice your USB thing is allowed to sip. no cap. πŸ’…


🌸 SYNOPSIS 🌸

int ab8500_charger_max_usb_curr (struct ab8500_charger *di , enum
ab8500_charger_link_status link_status );

that's the whole vibe β€” an int coming back at you, two args going in. πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • di β€” pointer to the ab8500_charger structure. it's giving "here's the charger object, do ur thing" energy.
  • link_status β€” the identified USB type. so what kind of USB we're dealing with, basically the main character of this function.

πŸ’œ DESCRIPTION πŸ’œ

Get the maximum current that is allowed to be drawn from the host based on the USB type. πŸ”₯

Returns error code in case of failure else 0 on success. so like... 0 = slay, anything else = something went off and it's telling you about it. 😭


⭐ SEE ALSO ⭐

Kernel file ./drivers/power/supply/ab8500_charger.c β€” and then the whole friend group, get comfy, this is a long one:

that's the whole group chat, all (9), all iconic. πŸ‘‘


and that's the page!! mwah πŸ’‹ β€” this lil beauty lives in ./drivers/power/supply and it's dated October 2026, so yeah, future-coded. go read the other ab8500_charger pages, they ate and left no crumbs. πŸŒˆπŸ’–

πŸ“¦ where this page comes from