efx_mcdi_rpc_async(9)

💖 efx_mcdi_rpc_async 💖

okay so bestie, this is the efx_mcdi_rpc_async page from the Kernel API Manual, section 9 ✨ it's giving “schedule an MCDI command to run asynchronously” and honestly the async energy is iconic 💅

🌸 NAME 🌸

• efx_mcdi_rpc_async — Schedule an MCDI command to run asynchronously

✨ SYNOPSIS ✨

int efx_mcdi_rpc_async (struct efx_nic *efx , unsigned int cmd , const
       efx_dword_t *inbuf , size_t inlen , size_t outlen ,
       efx_mcdi_async_completer *complete , unsigned long cookie );

💅 ARGUMENTS 💅

• efx — NIC through which to issue the command 🫶
• cmd — Command type number
• inbuf — Command parameters
• inlen — Length of command parameters, in bytes
• outlen — Length to allocate for response buffer, in bytes
• complete — Function to be called on completion or cancellation.
• cookie — Arbitrary value to be passed to complete.

🦋 DESCRIPTION 🦋

This function does not sleep and therefore may be called in atomic context. no lil nap, no vibe interruption 😴🚫 It will fail if event queues are disabled or if MCDI event completions have been disabled due to an error.

If it succeeds, the complete function will be called exactly once in atomic context, when one of the following occurs:

• (a) the completion event is received (in NAPI context)
• (b) event queues are disabled (in the process that disables them)
• (c) the request times-out (in timer context)

so yeah, that complete callback is a one-time exclusive event, bestie — exactly once, in atomic context 💖

🔥 SEE ALSO 🔥

• Kernel file ./drivers/net/ethernet/sfc/mcdi.c
• efx_mcdi_rpc(9)

that’s the whole page, bestie 🫶 source/version tea from ./drivers/net/ethernet/sfc, dated October 2026, for efx_mcdi_rpc_async(9) — slay and stay asynchronous 💅✨