STRUCT QCOM_RPM_MESSAGE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ 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