STRUCT AD5686_BUS_OPS(9)

💅 struct ad5686_bus_ops(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — today's main character is struct ad5686_bus_ops, and honestly? it's giving "bussin' bus ops." no cap, this lil struct is the whole personality of how a specific bus talks to the ad5686 DAC. 🎀

---

✨ NAME ✨

struct ad5686_bus_ops — bus specific read/write operations 🦋

like, literally the read/write hookup for whichever bus you're riding. iykyk.

---

🌸 SYNOPSIS 🌸

struct ad5686_bus_ops {
    int (*read)(struct ad5686_state *st, u8 addr);
    int (*write)(struct ad5686_state *st, u8 cmd, u8 addr, u16 val);
    int (*sync)(struct ad5686_state *st);
 };

okay the way that semicolon-and-brace alignment is slightly unhinged but we respect it 💀 (that stray leading space before the closing }; is canon, bestie, don't touch it 🙈).

---

👑 Members 👑

• read — reads a register value at the given address. cute, simple, does what it says on the tin 📖✨
• write — writes a command, address and value to the device. the full lil sandwich: cmd + addr + val 🥪💜
• sync — ensures the completion of the write operation. and it's optional! so if you don't need it, you don't gotta bring it to the party 🎉

fr fr, sync being optional is the one detail you don't wanna fumble — the other two are just there being iconic, but sync can ghost you and that's fine 💅

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/iio/dac/ad5686.h — go read it bestie, it's right there 📂
• struct ad5686_chip_info(9) — the chip info one 🧚
• struct ad5686_state(9) — the state one, aka the st your callbacks keep passing around 🌈

---

and that's the whole vibe check! no notes, ate and left no crumbs 🍓

sign-off time bestie 🫶 this lil gem lives over in ./drivers/iio/dac, stamped October 2026, and yeah — it's still called struct ad5686_bus_ops(9), periodt. ⭐😭💖