adxl313_is_act_inact_ac(9)

💅 adxl313_is_act_inact_ac(9)

okay bestie, welcome to the Kernel API Manual ✨ — this one's a little function from the IIO accelerometer world and honestly it's giving "small but mighty". Let's get into it 🎀

---

🌸 NAME

adxl313_is_act_inact_ac — the vibe check that tells you if AC coupling is enabled. that's it, that's the whole job 💖

---

✨ SYNOPSIS

int adxl313_is_act_inact_ac (struct adxl313_data *data , enum
       adxl313_activity_type type );

yeah she's a two-argument girly and she returns an int. no cap 🫶

---

🦋 ARGUMENTS

• data — the device data. like, the actual accelerometer's business. hand it over and the function knows who it's talking about 💜
• type — the activity or inactivity type. you're telling it which flavour of act/inact you're curious about 🍓

---

🔥 DESCRIPTION

so here's the tea ☕ — you pass in a type of activity or inactivity, combined with either AC coupling set, or it just defaults to DC coupling. then this function literally verifies whether that combination is currently enabled or not. main character energy of a checker function, honestly 👑

it doesn't set anything, bestie, it just looks and reports back. lowkey iconic 🌈

---

⭐ RETURN

if the provided activity type has AC coupling enabled, you get that. otherwise, a negative error value shows up to ruin the party 😭 so always check the return — fr fr 💀

---

🧚 SEE ALSO

• Kernel file ./drivers/iio/accel/adxl313_core.c
• adxl313_fifo_reset(9)
• adxl313_core_probe(9)

these are the siblings, go say hi 💫

---

ngl, if you're poking at adxl313_core.c anyway, you might as well read the whole thing. iykyk 🙈

---

and that's the whole page, babe 🎀 this came out of ./drivers/iio/accel and it's dated October 2026 — slay, go write some driver code, you got this 💅💖