ab8500_char...vbus_in_curr(9)
π ab8500_char...vbus_in_curr(9) β Kernel API Manual π
okay so bestie, welcome to the Kernel API Manual page for ab8500_char...vbus_in_curr(9). yes that name is a whole mouthful, and yes the truncation with the ... is giving "my crush's contact name got cut off in my phone" energy π but we move. this is a Linux kernel function, it lives in ./drivers/power/supply, and it's about telling your charger how much juice it's allowed to slurp from USB. let's get into it π«Ά
β¨ NAME β¨
ab8500_charger_set_vbus_in_curr β set VBUS input current limit π
like... it literally does what it says on the tin. no cap, this one's an icon.
πΈ SYNOPSIS πΈ
int ab8500_charger_set_vbus_in_curr (struct ab8500_charger *di , int
ich_in_ua );
that's the whole signature, copied exactly, don't come for me π
π¦ ARGUMENTS π¦
diβ pointer to theab8500_chargerstructure. it's the main character of this whole file, so bestie you're gonna be handing it around a lot β¨ich_in_uaβ the charger input current limit, in microampere. yes, micro. that's the unit. respect it π
π DESCRIPTION π
so what does it actually do? it sets the current that can be drawn from the USB host β‘ basically it's the bouncer at the club deciding how many amps get through the velvet rope, and the USB host is standing outside like "let me in" π
and if things go sideways? it returns an error code in case of failure. but else? 0 (on success) π so like, zero means we slayed. remember that, iykyk.
π SEE ALSO π
okay so this is the part where i list literally everything related, and there is... a lot. do not skip this. these are all (9) manual references and they're all part of the family, okay, i love them all equally π₯Ή
- Kernel file
./drivers/power/supply/ab8500_charger.cπ 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_max_usb_curr(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_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)
like, that's the whole extended friend group. every single one of them. no cuts, no skips, we don't do that here π
and that's a wrap bestie!! π this page is from ./drivers/power/supply, dated October 2026, and it's the ab8500_char...vbus_in_curr(9) entry of the Kernel API Manual. go set some current limits, stay hydrated, and remember: 0 means success πβ¨π¦
π¦ 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