m24lr_regmap_write(9)

✨ m24lr_regmap_write(9) ✨

okay bestie, so this is a page straight out of the Kernel API Manual and it's lowkey iconic — it's the m24lr_regmap_write function, and it's here to write your data using regmap with retry on failure. yes, retry on failure, she's persistent 💅

---

🌸 SYNOPSIS 🌸

ssize_t m24lr_regmap_write (struct regmap *regmap , const u8 *buf ,
size_t size , unsigned int offset );

like, that's the whole signature. take it in. 🫶

---

🎀 ARGUMENTS 🎀

• regmap — the regmap instance for the device, aka the whole vibe check for where your data's headed ✨
• buf — the buffer containing the data to write, like your little payload of truth 💖
• size — number of bytes to write, so she knows exactly how much she's serving 🍓
• offset — starting register address, the lil address where the whole thing kicks off 👑

---

🦋 DESCRIPTION 🦋

so here's the tea ☕ — this function attempts to write a block of data to the device, and it does it with retries and a timeout. very main character energy.

some M24LR devices may NACK I2C writes while an internal write operation is in progress 😭 like they're literally busy, bestie, don't take it personally. so this function retries the write operation with a short delay, over and over, until it succeeds or the timeout is reached. she does not give up easily. persistence slay 💅🔥

---

👑 RETURN 👑

• on success, you get the number of bytes written 💖
• if the write fails within the timeout window, you get -ETIMEDOUT 😭💀 that's your signal to go touch some grass and come back later.

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/nvmem/m24lr.c
• struct m24lr_chip(9)
• struct m24lr(9)
• m24lr_regmap_read(9)
• m24lr_write(9)
• m24lr_write_pass(9)

---

that's a wrap, bestie 🎀 this page lives in ./drivers/nvmem, and the version/date stamp on it is October 2026 — so like, she's from the future ✨🔮 no cap. mwah, go write some registers 💜🧚