ab8500_charg...get_property(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ab8500_charger_ac_get_property(9) ✨

okay so bestie, welcome to the Kernel API Manual 🎀 — yes the title up top gets truncated to ab8500_charg...get_property(9) because even manpage headers have a character limit, and honestly? relatable 💀. Anyway, sit down, hydrate, and let's talk about how we read AC/mains properties 💖

🌸 NAME 🌸

ab8500_charger_ac_get_property — get the ac/mains properties 🫶

✨ SYNOPSIS ✨

int ab8500_charger_ac_get_property (struct power_supply *psy , enum
power_supply_property psp , union power_supply_propval *val );

🦋 ARGUMENTS 🦋

  • psy — pointer to the power_supply structure. it's giving "the whole entire supply bestie" 👑
  • psp — pointer to the power_supply_property structure. like, which property are we even asking about rn 😭
  • val — pointer to the power_supply_propval union. this is where the answer goes to live, no cap 💅

🌈 DESCRIPTION 🌈

so this function?? it gets called when an application tries to get the ac/mains properties by reading the sysfs files. main character energy fr fr ⭐

the AC/Mains properties are online, present and voltage. periodt:

  • online — ac/mains charging is in progress or not 💖
  • present — presence of the ac/mains 🦋
  • voltage — AC/Mains voltage ⚡
heads up bestie: it Returns error code in case of failure else 0(on success) — so 0 means slay, anything else means we're not okay 😭

🧚 SEE ALSO 🧚

the kernel file ./drivers/power/supply/ab8500_charger.c, plus literally this whole friend group:

and that's the whole page bestie, you ate that 🍓

this little love letter lives in ./drivers/power/supply and it's stamped October 2026 if you ever need to cite your sources 💜 mwah, go read your sysfs files responsibly ✨💅

📦 where this page comes from