__qcom_smd_send(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

__qcom_smd_send β€” write data to smd channel πŸ’…

okay so real quick, bestie: this page is from the Kernel API Manual, and it's all about __qcom_smd_send. It's giving "let's push some bytes into an smd channel" energy, and we're gonna get into it ✨


πŸŽ€ SYNOPSIS πŸŽ€

int __qcom_smd_send (struct qcom_smd_channel *channel , const void *data
, int len , bool wait );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • channel β€” channel handle 🫢
  • data β€” buffer of data to write πŸ’–
  • len β€” number of bytes to write πŸŽ€
  • wait β€” flag to indicate if write can wait ⭐

✨ DESCRIPTION ✨

This is a blocking write of len bytes into the channel's tx ring buffer, and then it signals the remote end. Like, it's not gonna just shove stuff in and dip β€” no ma'am.

It will sleep until there is enough space available in the tx buffer, utilizing the fBLOCKREADINTR signaling mechanism to avoid polling. That's the whole vibe: wait for room, don't sit there spinning and checking over and over. Iconic, honestly πŸ˜­πŸ’œ


🌈 SEE ALSO 🌈


okay bye bestie πŸ’– cute little sign-off time: this page's footer says source/version is ./drivers/rpmsg, date is October 2026, and the page is __qcom_smd_send(9) β€” with the Kernel API Manual name already living near the top, periodt βœ¨πŸ¦‹

πŸ“¦ where this page comes from