mipi_dsi_du...te_seq_multi(9)
π mipi_dsi_dual_dcs_write_seq_multi(9)
okay so bestie, welcome to the Kernel API Manual β¨ β this page is literally about mipi_dsi_dual_dcs_write_seq_multi, and no cap, the name is giving "long but iconic." π
β¨ NAME β¨
mipi_dsi_dual_dcs_write_seq_multi β transmit a DCS command with payload to two dsi interfaces, one after the other π¦
Like, one command, two interfaces, in a row. The way that it justβ¦ does both. π
πΈ SYNOPSIS πΈ
mipi_dsi_dual_dcs_write_seq_multi (_ctx , _dsi1 , _dsi2 , _cmd , _seq...
);
yes, the trailing _seq... is exactly how it ships, don't come for me π
π ARGUMENTS π
_ctxβ context for multiple DSI transactions. it's the group chat, basically β it holds the state for the whole convo π«Ά_dsi1β first DSI interface, the one that gets to be the recipient of the packet. main character energy π_dsi2β second DSI interface, also a recipient of the packet. twin energy, fr fr π_cmdβ the command. the actual thing you're sending π¨_seqβ buffer containing the payload. the lil backpack of data the command carries around π
π§ DESCRIPTION π§
so here's the tea β β this macro will send the specified DCS command with payload twice, once per each of the two interfaces supplied. literally two interfaces, two sends, one macro call. slay. π
it's highkey useful for reducing duplication of code in panel drivers which use two parallel serial interfaces. like, why write it twice when you can write it once and let the macro eat? ate and left no crumbs π
β οΈ note that if an error occurs while transmitting the payload to the first DSI interface, the payload will not be sent to the second DSI interface. bestie, that's a real caveat β first one flops, second one doesn't even get the chance π
this macro will print errors for you, and error handling is optimized for callers that call this multiple times in a row. so likeβ¦ repeatedly calling it? that's the intended vibe. iykyk β¨
π₯ SEE ALSO π₯
- Kernel file
./include/drm/drm_mipi_dsi.hπ struct mipi_dsi_msg(9)struct mipi_dsi_packet(9)struct mipi_dsi_host_ops(9)struct mipi_dsi_host(9)struct mipi_dsi_device_info(9)struct mipi_dsi_device(9)struct mipi_dsi_multi_context(9)mipi_dsi_pixel_format_to_bpp(9)enum mipi_dsi_dcs_tear_mode(9)mipi_dsi_generic_write_seq_multi(9)mipi_dsi_generic_write_var_seq_multi(9)mipi_dsi_dcs_write_seq_multi(9)mipi_dsi_dcs_write_var_seq_multi(9)mipi_dsi_dual(9)mipi_dsi_dual_generic_write_seq_multi(9)struct mipi_dsi_driver(9)
the whole friend group, honestly. go say hi to all of them π«Άπ
and that's the page, bestie! π huge shoutout to ./include/drm for being the source, to the Kernel API Manual for hosting, and to October 2026 for the timestamp β iconic of all of them, periodt. βπΈ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms