ab8500_charg..._output_curr(9)
β¨ ab8500_charger_set_output_curr π
okay so real talk, bestie β this little cutie lives in the Kernel API Manual, and its whole entire personality is setting the charger output current. that's it. that's the vibe. π
πΈ NAME πΈ
ab8500_charger_set_output_curr β set charger output current, periodt π
π¦ SYNOPSIS π¦
int ab8500_charger_set_output_curr (struct ab8500_charger *di , int
ich_out_ua );
like, she takes two things and gives you back an int. iconic behavior ngl π₯
π ARGUMENTS π
diβ pointer to theab8500_chargerstructure. yes bestie, the whole struct, we're going in π«Άich_out_uaβ output charger current, in uA. that's microamps, so like, tiny units but big responsibility π
β¨ DESCRIPTION β¨
Set charger output current. that's the mission, that's the whole plot π
She returns an error code in case of failure, else 0 (on success). so like β 0 means slay, anything else means π. keep an eye on that return value, fr fr.
π SEE ALSO π
Kernel file ./drivers/power/supply/ab8500_charger.c β plus literally the whole extended friend group, no cap:
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_vbus_in_curr(9)ab8500_charger_set_main_in_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 i said. the whole group chat. π«Άπ
ngl bestie, if you're poking at charger current in the kernel, you already know what you're doing. go off π
and that's the tea π β this page comes from ./drivers/power/supply, stamped October 2026, and it's filed under the same ab8500_charg..._output_curr(9) header you scrolled in on. mwah πβ¨
π¦ 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