ads131m_write_reg_unlocked(9)

💅 ads131m_write_reg_unlocked(9) 💅

okay so this is a page from the Kernel API Manual bestie, and it is literally about writing one single register and then being a paranoid queen about it and verifying the ACK. obsessed. 🎀

---

✨ NAME ✨

ads131m_write_reg_unlocked — writes a single register and verifies the ACK. no cap, that's the whole job. 🫶

---

🌸 SYNOPSIS 🌸

int ads131m_write_reg_unlocked (struct ads131m_priv *priv , u8 reg , u16 val );

---

🦋 ARGUMENTS 🦋

• priv — the device private data structure. it's giving "everything you need to know about this device lives here" energy. 👑
• reg — the 8-bit register address. yes bestie, 8-bit, keep it cute. ⭐
• val — the 16-bit value you're gonna write in there. 16-bit, she's bigger. 💖

---

🔥 DESCRIPTION 🔥

so this function performs the full 3-cycle WREG operation with Input CRC. like, the whole ritual. not me doing four steps for three cycles, iykyk 😭

1. (Cycle 1) Sends WREG command, data, and its calculated CRC. 💅
2. (Cycle 2) Sends NULL+CRC to retrieve the response from Cycle 1. 🧚
3. Verifies the response is the correct ACK for the WREG. this is the vibe check fr fr ✅
4. (Cycle 3) Sends NULL+CRC to retrieve STATUS and check for CRC_ERR. 🚨

ngl bestie, if the ACK doesn't match or CRC_ERR shows up, that's a whole situation. the function will let you know via that return value below. 💀

---

🌈 RETURN 🌈

0 on success, or a negative error code. that's it, that's the tea. 🍓

---

💜 SEE ALSO 💜

• Kernel file ./drivers/iio/adc/ti-ads131m02.c
• ads131m_tx_frame_unlocked(9)
• ads131m_rx_frame_unlocked(9)
• ads131m_check_status_crc_err(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)

---

anyway mwah 💋 this little icon came from ./drivers/iio/adc and she's stamped October 2026, ads131m_write_reg_unlocked(9) forever and always, periodt. 🌟🫶