STRUCT AB8500_CHARGER_INTERRUPTS(9)
π struct ab8500_charger_interrupts(9) π
okay so bestie, you're reading the Kernel API Manual β this is the whole entire doc for struct ab8500_charger_interrupts, ab8500 interrupts, and honestly? it's giving tiny-but-iconic. two members. two. and yet the see-also list is a whole friend group π
β¨ NAME β¨
struct ab8500_charger_interrupts β ab8500 interrupts π
like, that's it, that's the name. short and slay.
πΈ SYNOPSIS πΈ
here's the literal shape of it, no cap:
struct ab8500_charger_interrupts {
char *name;
irqreturn_t (*isr)(int irq, void *data);
};
^^ that's the whole struct. two fields. main character energy in a two-line package honestly π
π¦ Members π¦
okay so here's the breakdown of the two fields, and yes i'm gonna be normal about it:
nameβ name of the interrupt π like, what this interrupt is called. its little nametag at the party.isrβ function pointer to the isr π₯ this is the handler function itself β it takesint irqandvoid *dataand returnsirqreturn_t, which is exactly what the signature up in the synopsis says. so don't come for me, it's literally in the code block bestie.
π reminder: the isr member is a function pointer, not a function you call directly by name β the signature in the struct is the whole truth. keep it exactly as written.
π SEE ALSO π
Kernel file ./drivers/power/supply/ab8500_charger.c β and then the entire extended universe of references, gathered here so you never have to ask "wait who else is in this file" ever again π«Ά
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_usb_get_property(9)ab8500_charger_init_hw_registers(9)
that's the whole page bestie, you ate it up π
and for the little sign-off moment: this one lives under ./drivers/power/supply, dated October 2026, and its footer name is the truncated-but-still-iconic struct ab850...r_interrupts(9). 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