mei_cl_irq_dma_map(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

mei_cl_irq_dma_map β€” bestie, this one sends a client dma map request, and it does it in irq_thread context ✨ (yes, interrupt-thread land, we're fancy like that)


✨ SYNOPSIS ✨

int mei_cl_irq_dma_map (struct mei_cl *cl , struct mei_cl_cb *cb ,
       struct list_head *cmpl_list );

That's the whole vibe check right there β€” returns an int, takes three things, done 🫢


🫢 ARGUMENTS 🫢

  • cl β€” the client πŸ’– that's it, that's the argument
  • cb β€” the callback block, lowkey where all the action lives
  • cmpl_list β€” the complete list, the "who's done" list, iconic behavior honestly

πŸŽ€ RETURN πŸŽ€

Returns 0 on success and an error otherwise β€” no cap, that's the whole deal 😭 so always check your return value, bestie, fr fr

ngl a nonzero return here means something went sideways, and the manpage does not elaborate, so don't go inventing meanings πŸ’€ just know: 0 = slay, anything else = not slay.

πŸ¦‹ SEE ALSO πŸ¦‹

The kernel file lives at ./drivers/misc/mei/client.c and honestly the whole friend group is tagged below β€” go read the rest of them, they're all giving main character energy πŸ‘‘

mei_me_cl_init(9),
mei_me_cl_get(9), mei_me_cl_release(9), mei_me_cl_put(9),
__mei_me_cl_del(9), mei_me_cl_del(9), mei_me_cl_add(9),
__mei_me_cl_by_uuid(9), mei_me_cl_by_uuid(9), mei_me_cl_by_id(9),
__mei_me_cl_by_uuid_id(9), mei_me_cl_by_uuid_id(9),
mei_me_cl_rm_by_uuid(9), mei_me_cl_rm_all(9), mei_io_cb_free(9),
mei_tx_cb_enqueue(9), mei_tx_cb_dequeue(9), mei_cl_set_read_by_fp(9),
mei_io_cb_init(9), mei_io_list_flush_cl(9), mei_io_tx_list_free_cl(9),
mei_io_rd_list_free_fp(9), mei_cl_free_pending(9), mei_cl_alloc_cb(9),
mei_cl_enqueue_ctrl_wr_cb(9), mei_cl_read_cb(9), mei_cl_flush_queues(9),
mei_cl_init(9), mei_cl_allocate(9), mei_cl_link(9), mei_cl_unlink(9),
mei_hbuf_acquire(9), mei_cl_wake_all(9), mei_cl_set_disconnected(9),
mei_cl_irq_disconnect(9), __mei_cl_disconnect(9), mei_cl_disconnect(9),
mei_cl_is_other_connecting(9), mei_cl_send_connect(9),
mei_cl_irq_connect(9), mei_cl_connect(9), mei_cl_alloc_linked(9),
mei_cl_tx_flow_ctrl_creds(9), mei_cl_tx_flow_ctrl_creds_reduce(9),
mei_cl_vtag_alloc(9), mei_cl_fp_by_vtag(9),
mei_cl_reset_read_by_vtag(9), mei_cl_read_vtag_add_fc(9),
mei_cl_vt_support_check(9), mei_cl_add_rd_completed(9),
mei_cl_del_rd_completed(9), mei_cl_notify_fop2req(9),
mei_cl_notify_req2fop(9), mei_cl_irq_notify(9),
mei_cl_notify_request(9), mei_cl_notify(9), mei_cl_notify_get(9),
mei_cl_read_start(9), mei_msg_hdr_init(9), mei_cl_irq_write(9),
mei_cl_write(9), mei_cl_complete(9), mei_cl_all_disconnect(9),
mei_cl_irq_dma_unmap(9), mei_cl_dma_alloc_and_map(9),
mei_cl_dma_unmap(9)

🌸 okay that's the page!! 🌸 this lil number ships out of ./drivers/misc/mei, dated October 2026, and it's literally the mei_cl_irq_dma_map(9) page β€” that's the footer, that's the sign-off, we're done here, ily, go read your kernel source πŸ’œπŸŽ€πŸ¦‹

πŸ“¦ where this page comes from