mei_cldev_send_gsc_command(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mei_cldev_send_gsc_command β€” the manual, but make it make sense

okay so bestie, welcome to the Kernel API Manual page for mei_cldev_send_gsc_command(9), and trust me, this one's a whole little quest. it's the function you call when you need to slide a gsc command over to gsc β€” you send it a gsl mei message, and then you sit there with your iced coffee waiting for gsc to reply. no cap, that's literally the entire plot. πŸŽ€


✨ NAME ✨

mei_cldev_send_gsc_command β€” sends a gsc command, by sending a gsl mei message to gsc and receiving reply from gsc πŸ¦‹


🌸 SYNOPSIS 🌸

ssize_t mei_cldev_send_gsc_command (struct mei_cl_device *cldev , u8
client_id , u32 fence_id , struct scatterlist *sg_in , size_t
total_in_len , struct scatterlist *sg_out );

πŸ’– ARGUMENTS πŸ’–

okay, the cast of characters, one by one:

  • cldev β€” the me client device, aka the main character of this whole operation πŸ‘‘
  • client_id β€” the client id you're sending the command to. like, who's this addressed to, yk? πŸ’Œ
  • fence_id β€” the fence id you're sending the command to πŸ”₯
  • sg_in β€” a scatter gather list holding the addresses for the rx message buffer 🌈
  • total_in_len β€” total length of data in the in sg. heads up though: this can be less than the sum of the buffer sizes, so don't go assuming, bestie 🫢
  • sg_out β€” a scatter gather list holding the addresses for the tx message buffer ✨

⭐ RETURN ⭐

what you get back, lowkey important:

  • written size in bytes πŸ’…
  • < 0 on error πŸ’€

🧚 SEE ALSO 🧚

go read these, fr fr. the kernel file is ./drivers/misc/mei/bus.c and the squad is: __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_mtu(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_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).

that's the whole group chat. go say hi. πŸ’œ


ok that's the page!! mwah πŸ’‹

and before you close the tab β€” this icon lives at ./drivers/misc/mei, dated October 2026, still answering to mei_cldev_send_gsc_command(9). slay. πŸ“πŸŒΈ

πŸ“¦ where this page comes from