ab8500_charger_max_usb_curr(9)
π 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 theab8500_chargerstructure. 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:
struct ab8500_charger_interrupts(9)struct ab8500_charger(9)ab8500_power_supply_changed(9)ab8500_charger_get_ac_voltage(9)ab8500_charger_ac_cv(9)ab8500_charger_get_vbus_voltage(9)ab8500_charger_get_usb_current(9)ab8500_charger_get_ac_current(9)ab8500_charger_usb_cv(9)ab8500_charger_detect_chargers(9)ab8500_charger_read_usb_type(9)ab8500_charger_detect_usb_type(9)ab8500_charger_get_usb_cur(9)ab8500_charger_check_continue_stepping(9)ab8500_charger_set_current(9)ab8500_charger_set_vbus_in_curr(9)ab8500_charger_set_main_in_curr(9)ab8500_charger_set_output_curr(9)ab8500_charger_led_en(9)ab8500_charger_ac_en(9)ab8500_charger_usb_en(9)ab8500_charger_usb_check_enable(9)ab8500_charger_ac_check_enable(9)ab8500_charger_watchdog_kick(9)ab8500_charger_update_charger_current(9)ab8500_charger_check_vbat_work(9)ab8500_charger_check_hw_failure_work(9)ab8500_charger_kick_watchdog_work(9)ab8500_charger_ac_work(9)ab8500_charger_detect_usb_type_work(9)ab8500_charger_usb_link_attach_work(9)ab8500_charger_usb_link_status_work(9)ab8500_charger_check_usbchargernotok_work(9)ab8500_charger_check_main_thermal_prot_work(9)ab8500_charger_check_usb_thermal_prot_work(9)ab8500_charger_mainchunplugdet_handler(9)ab8500_charger_mainchplugdet_handler(9)ab8500_charger_mainextchnotok_handler(9)ab8500_charger_mainchthprotr_handler(9)ab8500_charger_mainchthprotf_handler(9)ab8500_charger_vbusdetf_handler(9)ab8500_charger_vbusdetr_handler(9)ab8500_charger_usblinkstatus_handler(9)ab8500_charger_usbchthprotr_handler(9)ab8500_charger_usbchthprotf_handler(9)ab8500_charger_usbchargernotokr_handler(9)ab8500_charger_chwdexp_handler(9)ab8500_charger_vbuschdropend_handler(9)ab8500_charger_vbusovv_handler(9)ab8500_charger_ac_get_property(9)ab8500_charger_usb_get_property(9)ab8500_charger_init_hw_registers(9)
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
- 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