mlx5_cmd_do(9)

💅 mlx5_cmd_do — the kernel API manual, bestie edition ✨

Okay so bestie, welcome to the mlx5_cmd_do(9)</p> page — it lives in the Kernel API Manual and it's genuinely one of those little functions that does exactly one thing and does it iconically. 🎀

🌸 NAME 🌸

mlx5_cmd_do — runs an fw command and waits for it to finish, periodt. 💅

And here's the tea: unlike mlx5_cmd_exec, this function will not translate or intercept outbox.status, and it will return -EREMOTEIO when outbox.status != MLX5_CMD_STAT_OK. No cap, that's the whole personality. 👑

✨ SYNOPSIS ✨

int mlx5_cmd_do (struct mlx5_core_dev *dev , void *in , int in_size ,
void *out , int out_size );

She takes five things, gives you back an int, and doesn't elaborate further. 🫶

🦋 ARGUMENTS 🦋

• dev — the mlx5 core device. the main character, lowkey. 🌟
• in — the inbox mlx5_ifc command buffer. this is what you're sending, bestie. 📨
• in_size — size of that inbox buffer. gotta know how much you're sending. 📏
• out — the outbox mlx5_ifc buffer. this is where the answer comes back. 📬
• out_size — size of the outbox. same energy, different buffer. 💌

🔥 RETURN 🔥

• -EREMOTEIO — the command was executed by FW, but outbox.status != MLX5_CMD_STAT_OK. > ⚠️ bestie listen to me: the caller must check FW outbox status. this is not optional, this is a whole vibe check you have to do yourself. 💀
• 0 — command execution was successful, outbox.status == MLX5_CMD_STAT_OK. slay. ✅
• < 0 — command execution couldn't be performed by firmware or driver. not her fault, she tried. 😭

🧚 SEE ALSO 🧚

• Kernel file ./drivers/net/ethernet/mellanox/mlx5/core/cmd.c — go read the source, iykyk 📖
• mlx5_cmd_exec(9)
• mlx5_cmd_exec_polling(9)
• mlx5_cmd_cleanup_async_ctx(9)

go off, read all of them, they're all part of the same friend group fr fr 🫶✨

and that's the page!! 🦋 cute little sign-off: this one came from ./drivers/net/ethernet/mellano... and it's dated October 2026 — save the date, bestie, mlx5_cmd_do(9) never goes out of style 💖🌈👑