__qcom_smd_send(9)
πΈ 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 π
- Kernel file
./drivers/rpmsg/qcom_smd.c struct qcom_smd_edge(9)struct qcom_smd_channel(9)struct qcom_smd_alloc_entry(9)qcom_smd_register_edge(9)qcom_smd_unregister_edge(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms