cros_ec_sensors_capture(9)

📦 version 7.3.1, in nixpkgs unstable

💅 cros_ec_sensors_capture(9) — from the Kernel API Manual, bestie

okay so first things first: yes, this is a page from the Kernel API Manual (section 9, kernel developer vibes only ✨), and we're talking about cros_ec_sensors_capture. it's short, it's sweet, and it's lowkey the moment the magic happens. let's get into it 🫶

🌸 NAME 🌸

cros_ec_sensors_capture — the trigger handler function. that's it, that's the whole name. icon behavior honestly 👑

✨ SYNOPSIS ✨

irqreturn_t cros_ec_sensors_capture (int irq , void *p );

look at her. so tidy. so purposeful. 🎀

🦋 ARGUMENTS 🦋

  • irq — the interrupt number. yeah, the actual number of the interrupt. that one. 🔥
  • p — a pointer to the poll function. like, the pollfunc gets to hang out here. bestie brought a friend 💜

💖 DESCRIPTION 💖

okay so here's the tea ☕ — on a trigger event occurring, if the pollfunc is attached, then this handler gets called as a threaded interrupt (and hence it may sleep 😴). yes, it can sleep! that's the whole point of the threaded business, iykyk.

and what is she responsible for? grabbing data from the device and pushing it into the associated buffer. that's literally it. she grabs, she pushes, she leaves. main character energy fr fr 🌟

🌈 RETURN 🌈

IRQ_HANDLED — that's it. she handled it. periodt. 💅

ngl there is exactly one return value listed here, so don't @ me about edge cases, this is what the page says 🫶

🧚 SEE ALSO 🧚

the whole friend group, no cap:

go read them, they're all slay, you'll be obsessed 🍓

and that's the page!! cute little sign-off time: this one comes from ./drivers/iio/common/cros_ec_s... and the date on it is October 2026, all wrapped up as cros_ec_sensors_capture(9) 🌸💖 mwah, go read some kernel source, ily 🫶⭐

📦 where this page comes from