STRUCT QCOM_RPM_MESSAGE(9)
π NAME π
struct qcom_rpm_message β response message from the rpm. And yes bestie, this is straight out of the Kernel API Manual, so you know it's official.
β¨ SYNOPSIS β¨
struct qcom_rpm_message {
__le32 msg_type;
__le32 length;
union {
__le32 msg_id;
u8 message[];
};
};
π Members π
msg_type(__le32) β indicator of the type of message. It's giving "what kind of message is this?" energy.length(__le32) β the size of this message, including the message header. So yes, the header counts, no cap.{unnamed_union}β anonymous. Literally an unnamed union doing its anonymous little thing.msg_id(__le32) β message id.message(u8 message[]) β textual message from the rpm. The actual words, bestie.
πΈ Description πΈ
Multiple of these messages can be stacked in an rpm message. That's the whole vibe: they pile up together inside one rpm message.
π SEE ALSO π
Kernel file ./drivers/soc/qcom/smd-rpm.c β plus struct qcom_smd_rpm(9), struct qcom_rpm_header(9), struct qcom_rpm_request(9), and qcom_rpm_smd_write(9). Go read those next, bestie, they're all linked up. π«Ά
Cute little sign-off: this page comes from ./drivers/soc/qcom, dated October 2026, and it's all about struct qcom_rpm_message(9). 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