ads131m_chec...atus_crc_err(9)

✨ ads131m_check_status_crc_err ✨

okay bestie, welcome to the Kernel API Manual — this one's about ads131m_check_status_crc_err, and yes the page title gets truncated like that, it's giving "my name is too long for the tab bar" energy 💅 but we move.

---

🌸 NAME 🌸

ads131m_check_status_crc_err — Checks for an Input CRC error. that's the whole vibe, she checks for CRC errors on the input side 🎀

🦋 SYNOPSIS 🦋

int ads131m_check_status_crc_err (struct ads131m_priv *priv );

💖 ARGUMENTS 💖

• priv — Device private data structure. yeah that's it, that's the whole argument list, she only needs her one (1) struct 🫶

🔥 DESCRIPTION 🔥

okay so here's what she actually does: she sends a NULL command to fetch the STATUS register, then checks the CRC_ERR bit. literally that's the whole job.

and why, you ask? because this is how you verify the integrity of the previous command (like RREG or WREG). so she's the vibe check for whatever you just did — if the last command came through garbled, she'll know 👀

⭐ RETURN ⭐

• 0 on success — slay, we're clean 💜
• -EIO if the CRC_ERR bit is set — nope, something went wrong, the frame is sus 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/iio/adc/ti-ads131m02.c

and her whole friend group, fr fr:

• ads131m_tx_frame_unlocked(9)
• ads131m_rx_frame_unlocked(9)
• ads131m_write_reg_unlocked(9)
• ads131m_read_reg_unlocked(9)
• ads131m_rmw_reg(9)
• ads131m_verify_output_crc(9)
• ads131m_adc_read(9)
• ads131m_hw_reset(9)
• ads131m_sw_reset(9)
• ads131m_reset(9)
• ads131m_hw_init(9)
• ads131m_parse_clock(9)

---

ngl bestie, if you're getting -EIO back from this one, go check that previous RREG/WREG — the CRC said no and she does not bluff 🙈

and that's the page!! brought to you from ./drivers/iio/adc, dated October 2026 — ily, go verify your frames, periodt 🧚‍♀️🎀