ab8500_char...get_property(9)
π ab8500_charger_usb_get_property β from the Kernel API Manual π
okay bestie, so this is a page straight out of the Kernel API Manual and it's literally the story of one function that just wants to tell you about your USB charger. sit down, hydrate, let's go β¨
πΈ NAME πΈ
ab8500_charger_usb_get_property β get the usb properties π«Ά
β SYNOPSIS β
int ab8500_charger_usb_get_property (struct power_supply *psy , enum
power_supply_property psp , union power_supply_propval *val );
π ARGUMENTS π
psyβ pointer to thepower_supplystructure. this is the main character of the whole operation, no cap π«Άpspβ pointer to thepower_supply_propertystructure. yes it's spelledpsp, we don't make the rules πvalβ pointer to thepower_supply_propvalunion. the little vessel where the answer gets dropped π
π¦ DESCRIPTION π¦
so this function gets called when an application tries to get the usb properties by reading the sysfs files. literally the plug-and-ask moment, iykyk πβ¨
the USB properties are, in order: online, present and voltage β and here's what each one is serving:
- online β usb charging is in progress or not
- present β presence of the usb
- voltage β vbus voltage
it returns an error code in case of failure, else 0 (on success). that's it, that's the whole vibe check π
π SEE ALSO π
kernel file ./drivers/power/supply/ab8500_charger.c β and honestly the whole extended friend group:
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_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_init_hw_registers(9)
lowkey that's a whole friend group and you're gonna want to know all of them, bestie. read the whole roster, fr fr π
and that's the page! πΈ sourced from ./drivers/power/supply, dated October 2026, filed under ab8500_char...get_property(9) in the Kernel API Manual β she ate, she left no crumbs, periodt π
β¨π
π¦ 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