mei_cldev_mtu(9)

💅 NAME 💅 — mei_cldev_mtu(9) from the Kernel API Manual

okay so bestie, mei_cldev_mtu is literally the max message that a client can send and receive. that's the whole assignment, no cap. 💖

✨ SYNOPSIS ✨

size_t mei_cldev_mtu (const struct mei_cl_device *cldev );

🎀 ARGUMENTS 🎀

• cldev — the mei client device. she's the one and only argument, lowkey simple like that. 🫶

🦋 RETURN 🦋

It hands you back the mtu — or 0 if the client is not connected. yep, that's the vibe check. 💀

🌈 SEE ALSO 🌈

The Kernel file called out here is ./drivers/misc/mei/bus.c, and then there's this whole iconic squad of references, iykyk:

• __mei_cl_send(9)
• __mei_cl_send_timeout(9)
• __mei_cl_recv(9)
• mei_cldev_send_vtag(9)
• mei_cldev_send_vtag_timeout(9)
• mei_cldev_recv_vtag(9)
• mei_cldev_recv_timeout(9)
• mei_cldev_recv_vtag_timeout(9)
• mei_cldev_send(9)
• mei_cldev_send_timeout(9)
• mei_cldev_recv(9)
• mei_cl_bus_rx_work(9)
• mei_cl_bus_notif_work(9)
• mei_cl_bus_notify_event(9)
• mei_cl_bus_rx_event(9)
• mei_cldev_register_rx_cb(9)
• mei_cldev_register_notif_cb(9)
• mei_cldev_get_drvdata(9)
• mei_cldev_set_drvdata(9)
• mei_cldev_uuid(9)
• mei_cldev_ver(9)
• mei_cldev_enabled(9)
• mei_cl_bus_module_get(9)
• mei_cl_bus_module_put(9)
• mei_cl_bus_vtag(9)
• mei_cl_bus_vtag_alloc(9)
• mei_cl_bus_vtag_free(9)
• mei_cldev_enable(9)
• mei_cldev_unregister_callbacks(9)
• mei_cldev_disable(9)
• mei_cldev_send_gsc_command(9)
• mei_cl_device_find(9)
• mei_cl_device_match(9)
• mei_cl_device_probe(9)
• mei_cl_device_remove(9)
• mei_cl_device_uevent(9)
• mei_cl_bus_set_name(9)
• mei_cl_bus_dev_alloc(9)
• mei_cl_bus_dev_setup(9)
• mei_cl_bus_dev_add(9)
• mei_cl_bus_dev_stop(9)
• mei_cl_bus_dev_destroy(9)
• mei_cl_bus_remove_device(9)
• mei_cl_bus_remove_devices(9)
• mei_cl_bus_dev_init(9)
• mei_cl_bus_rescan(9)

xoxo, from ./drivers/misc/mei, dated October 2026 — mei_cldev_mtu(9) out, bestie 🫶💖