ab8500_charg...pend_handler(9)
β¨ ab8500_charger_vbuschdropend_handler β¨
okay bestie, welcome to the Kernel API Manual π this one's a lil baby page but it's iconic in its own way. sit down, grab a strawberry π, and let's get into it.
πΈ NAME πΈ
ab8500_charger_vbuschdropend_handler β literally the handler for when the VBUS drop is removed π
that's it, that's the vibe.
π¦ SYNOPSIS π¦
irqreturn_t ab8500_charger_vbuschdropend_handler (int irq , void *_di );
like, it returns an irqreturn_t and takes two things. so demure. so mindful. no cap. β¨
π ARGUMENTS π
irqβ the interrupt number π« just the number of the interrupt we're dealing with, iykyk._diβ a pointer to theab8500_chargerstructure π«Ά like, it'svoid *but bestie it's really anab8500_chargerin there.
π DESCRIPTION π
so what does it do? it returns IRQ status(IRQ_HANDLED) β periodt. π that's the whole description, that's the tea.
like yeah, it's a short one. not every handler needs a whole monologue. main character energy is knowing when to be brief. π§
π SEE ALSO π
okay this is the part where it goes OFF π₯ like genuinely the longest part of the page, and honestly? slay. go read these, bestie:
- Kernel file
./drivers/power/supply/ab8500_charger.c - 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_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 whole friend group right there π every single one of them got an invite to the function-reference party and they ALL showed up.
π‘ lowkey reminder that this whole page lives in ./drivers/power/supply β that's the neighborhood, bestie. π‘
and that's the page!! π mwah. signed, sealed, delivered from ./drivers/power/supply, dated October 2026, and titled ab8500_charg...pend_handler(9) β yes the title is truncated with the lil ... and we're keeping it exactly like that because that's what the original says and we don't do character assassination here π
β¨ bye bestie, go read your kernel source π¦
π¦ 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