devfreq_event_get_event(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devfreq_event_get_event — straight out of the Kernel API Manual ✨

okay so bestie, picture this: you've got a devfreq-event device doing its whole little performance-monitoring thing, and you need the actual numbers out of it. that's this function. it's the little goblin that hands you the receipts. 🧾

🌸 NAME

devfreq_event_get_event — grab the {load|total}_count from a devfreq-event dev. yes, those curly braces are doing their whole "either one, babes" thing and they ate. 👑

✨ SYNOPSIS

int devfreq_event_get_event (struct devfreq_event_dev *edev , struct
       devfreq_event_data *edata );

🎀 ARGUMENTS

  • edev — the devfreq-event device. your main character, the one you're here for. 🫶
  • edata — the calculated data of the devfreq-event device. this is where the tea gets poured. 🍓

🦋 DESCRIPTION

lowkey important heads-up: this function gets the calculated event data from the devfreq-event dev after stoping the progress of the whole sequence of devfreq-event dev. (their spelling, not mine 💅)

so like — numbers first, whole sequence paused. that's the vibe. don't skip that part, it's literally the one note they gave us. 😭

ngl, "after stoping the progress of whole sequence" is doing a lot of heavy lifting in one sentence, but the point is clear: you only pull the calculated data once the entire devfreq-event dev sequence has been stopped. periodt.

💜 SEE ALSO

that's the whole page bestie, go forth and read your counters 🌈⭐

this little love letter came to you from ./drivers/devfreq, dated October 2026 — no cap, that's the version and the date, screenshot it 💖🎀

devfreq_event_get_event(9) 🦋

📦 where this page comes from