ab8500_charg...rotr_handler(9)
πΈ ab8500_charg...rotr_handler(9) πΈ
okay bestie, welcome to the Kernel API Manual π
this one's a lil niche but we're gonna slay it β today's main character is ab8500_charg...rotr_handler(9), which honestly is the most mysterious-looking name in the whole kernel doc set (yes, the dots are canon, don't @ me π).
β¨ NAME β¨
ab8500_charger_mainchthprotr_handler β the die temp is above the main charger thermal protection threshold ππ₯ like baby it got HOT.
π¦ SYNOPSIS π¦
irqreturn_t ab8500_charger_mainchthprotr_handler (int irq , void *_di );
that's it. that's the whole signature. iconic, honestly π
π ARGUMENTS π
irqβ the interrupt number, i.e. which interrupt came knocking π_diβ a pointer to theab8500_chargerstructure, aka the whole charger vibe in struct form π«Ά
π DESCRIPTION π
okay so when the main charger's die temperature goes above the thermal protection threshold, this handler gets called, and it returns the IRQ status, IRQ_HANDLED β
that's the entire bit. no notes. periodt.
lowkey obsessed with how short this one is β not every function needs a whole saga, some are just here to do one thing and do it gorgeously π
π SEE ALSO π
the girlies in the same file β kernel file ./drivers/power/supply/ab8500_charger.c β plus the whole extended friend group, in the exact order the manual lists them π§:
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_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)
fr fr that's a LOT of friends, but every single one of them is here, no skips, no cuts π«‘β¨
and that's the whole page bestie!! lived under ./drivers/power/supply, dated October 2026, and yeah the title says ab8500_charg...rotr_handler(9) again at the bottom too because the kernel manual believes in symmetry π mwah, go read the other 52 pages, iykyk π¦
π¦ 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