regmap_mult...ite_bypassed(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 regmap_mult...ite_bypassed(9) 🎀

okay so this is a page from the Kernel API Manual, bestie, and it's about regmap_multi_reg_write_bypassed(9) — yes the title got cutely truncated up top but we know her full name, don't worry 💅

✨ NAME ✨

regmap_multi_reg_write_bypassed — write multiple registers to the device but not the cache. she's giving "I'll tell the hardware, I just won't tell the cache" 🙈

🌸 SYNOPSIS 🌸

int regmap_multi_reg_write_bypassed (struct regmap *map , const struct reg_sequence *regs , int num_regs );

🦋 ARGUMENTS 🦋

  • map — the register map you're writing to. your main character struct, literally 💖
  • regs — an array of structures, and each one contains the register + value that's gonna be written. it's a whole little lineup of glow-ups ✨
  • num_regs — the number of registers to write. count 'em, don't guess 🫶

💜 DESCRIPTION 💜

So what she does is: write multiple registers to the device but not the cache, and the set of registers gets supplied in any order. no sorting required, she's flexible like that 🌈

This function is intended to be used for writing a large block of data atomically to the device in a single transfer — for those I2C client devices that implement this alternative block write mode. one transfer, all the data, no crumbs. iconic behavior ngl 🔥

A value of zero will be returned on success, and a negative errno will be returned in error cases. so like, 0 = slay, negative errno = 😭

fr fr tho: zero is success, negative errno is the bad timeline. memorize it, it's on the vibe check 👑

👑 SEE ALSO 👑

and that's the whole page, bestie, you ate 💅✨ this one lives in ./drivers/base/regmap and it's dated October 2026 — so like, mark your calendar and stan responsibly 🎀🦋💖

📦 where this page comes from