ab8500_char...tokr_handler(9)

💅 ab8500_char...tokr_handler(9) 💅

okay so bestie, this page lives in the Kernel API Manual and it's about one very specific little interrupt handler. her name is ab8500_charger_usbchargernotokr_handler and honestly the name is longer than the function, but we move 💖

---

✨ NAME ✨

ab8500_charger_usbchargernotokr_handler — USB charger not ok detected 🫶

like, she's the one who gets pinged when the USB charger situation is giving... not ok. no cap.

---

🌸 SYNOPSIS 🌸

irqreturn_t ab8500_charger_usbchargernotokr_handler (int irq , void *_di
);

---

🎀 ARGUMENTS 🎀

• irq — the interrupt number, aka which interrupt woke her up 💅
• _di — a pointer to the ab8500_charger structure. that's the void * bestie, she's carrying the charger struct in there 🦋

---

💜 DESCRIPTION 💜

Returns IRQ status (IRQ_HANDLED). that's it. that's the whole vibe. she handles the interrupt and hands back IRQ_HANDLED, slay ⭐

---

🌈 SEE ALSO 🌈

first up, the kernel file this all lives in: ./drivers/power/supply/ab8500_charger.c 📁

then the whole friend group, and yes we're listing every single one because they all ate 💅:

• 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_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)

---

and that's the whole page, hope that cleared things up bestie 🧚💜 drop a 💖 if you're the ab8500_char...tokr_handler(9) manual page, sourced from ./drivers/power/supply, dated October 2026, and yes we're still using that exact same truncated title at the top and bottom because that's just her name now 😭✨