ab8500_charg...sovv_handler(9)
π ab8500_charg...sovv_handler(9) π
okay so bestie, you're looking at ab8500_charg...sovv_handler(9) β that's the page title, and it lives in the Kernel API Manual, section 9 (the kernel-functions section, iykyk). Come sit with me, this one's a little cutie. π«Ά
β¨ NAME β¨
ab8500_charger_vbusovv_handler β literally the handler for when VBUS overvoltage gets detected. That's it, that's the whole vibe. β‘
πΈ SYNOPSIS πΈ
irqreturn_t ab8500_charger_vbusovv_handler (int irq , void *_di );
no cap, that's the whole signature. gorgeous. π
π ARGUMENTS π
irqβ the interrupt number, aka which interrupt we're talking about. it's giving "hi, it's me, the IRQ." π_diβ a pointer to theab8500_chargerstructure. it's thevoid *main character of this function, ngl. π«Ά
π¦ DESCRIPTION π¦
so what does it actually do? it returns the IRQ status IRQ_HANDLED. that's the whole thing. short and iconic, like a good text back. periodt. β¨
fr fr, that's all the description says β this little function handles the VBUS overvoltage interrupt and tells the kernel IRQ_HANDLED. no extra lore, don't let anyone tell you otherwise. π
π₯ SEE ALSO π₯
bestie there are SO many siblings, buckle up. the kernel file this all lives in is ./drivers/power/supply/ab8500_charger.c, and here's the whole 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_ac_get_property(9)ab8500_charger_usb_get_property(9)ab8500_charger_init_hw_registers(9)
like I said. a whole friend group. π but every single one of them is important, go say hi. π
and that's the page!! π§ this one came from ./drivers/power/supply (that's the source/version bit, slay) and it's dated October 2026. love that for us. byeee bestie, go handle those interrupts ππ
π¦ 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