ab8500_charg...imer_expired(9)

🌸 NAME 🌸

okay bestie, welcome to the Kernel API Manual page ab8500_charg...imer_expired(9). The function it’s hyping up is ab8500_chargalg_safety_timer_expired — Expiration of the safety timer. That’s the whole name, no cap. 💖

✨ SYNOPSIS ✨

The signature is literally this, character for character:

enum hrtimer_restart ab8500_chargalg_safety_timer_expired (struct
hrtimer *timer );

So yes, it hands back an enum hrtimer_restart, and it takes one struct hrtimer *timer. Slay. 🎀

🎀 ARGUMENTS 🎀

• timer — pointer to the hrtimer structure. That’s the one and only argument, bestie. 🫶

💅 DESCRIPTION 💅

When the safety timer for the charger expires, this function gets called. That’s the trigger, periodt. ⏰✨

🦋 SEE ALSO 🦋

If you’re doing a little charger-algorithm lore deep dive, these are the friends to check:

• Kernel file: ./drivers/power/supply/ab8500_chargalg.c
• struct ab8500_charge_curr_maximization(9)
• struct ab8500_chargalg(9)
• ab8500_chargalg_maintenance_timer_expired(9)
• ab8500_chargalg_state_to(9)
• ab8500_chargalg_check_charger_connection(9)
• ab8500_chargalg_start_safety_timer(9)
• ab8500_chargalg_stop_safety_timer(9)
• ab8500_chargalg_start_maintenance_timer(9)
• ab8500_chargalg_stop_maintenance_timer(9)
• ab8500_chargalg_kick_watchdog(9)
• ab8500_chargalg_ac_en(9)
• ab8500_chargalg_usb_en(9)
• ab8500_chargalg_update_chg_curr(9)
• ab8500_chargalg_stop_charging(9)
• ab8500_chargalg_hold_charging(9)
• ab8500_chargalg_start_charging(9)
• ab8500_chargalg_check_temp(9)
• ab8500_chargalg_check_charger_voltage(9)
• ab8500_chargalg_end_of_charge(9)
• ab8500_chargalg_chg_curr_maxim(9)
• ab8500_chargalg_external_power_changed(9)
• ab8500_chargalg_time_to_restart(9)
• ab8500_chargalg_algorithm(9)
• ab8500_chargalg_periodic_work(9)
• ab8500_chargalg_wd_work(9)
• ab8500_chargalg_work(9)
• ab8500_chargalg_get_property(9)

mwah 💋 — the footer’s source/version info is ./drivers/power/supply, the date is October 2026, and the manual tag is ab8500_charg...imer_expired(9). 🧚💜