mipi_dsi_du..._write_multi(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

Bestie, welcome to the Kernel API Manual page for mipi_dsi_du..._write_multi(9) — yes, that’s the title, abbreviated and iconic. The function it’s actually documenting is mipi_dsi_dual_generic_write_multi, and it’s literally mipi_dsi_generic_write_multi() for two dsi channels, one after the other. Periodt. 💅

✨ SYNOPSIS ✨

Okay so the signature is giving very important C vibes. Here it is exactly, no edits, fr fr:

void mipi_dsi_dual_generic_write_multi (struct mipi_dsi_multi_context *ctx , struct mipi_dsi_device *dsi1 , struct mipi_dsi_device *dsi2 , const void *payload , size_t size );

🎀 ARGUMENTS 🎀

Here’s the vibe check on every argument, and yes, all of them matter:

  • ctx — Context for multiple DSI transactions. It’s the little state bag for the multi-transaction situation. 🫶
  • dsi1 — First dsi channel to write buffer to. The first main character channel.
  • dsi2 — Second dsi channel to write buffer to. The second main character channel, obviously.
  • payload — Buffer containing the payload. This is the actual stuff being sent. 🍓
  • size — Size of payload buffer. Gotta know how much payload is payloading. 😭

💅 DESCRIPTION 💅

Okay so this function is a wrapper around mipi_dsi_generic_write_multi, and it allows the user to conveniently write to two dsi channels, one after the other. That’s the whole main character energy: generic write, but for two dsi channels back-to-back. No cap. 🦋

🦋 SEE ALSO 🦋

These are the linked manual pages and the kernel file mentioned, all kept exactly as-is because we do not mess with references, iykyk. 💖

And that’s the footer tea, bestie: this page comes from ./drivers/gpu/drm, dated October 2026, with the page title mipi_dsi_du..._write_multi(9). Obsessed. 🎀✨

📦 where this page comes from