STRUCT IPC_MEM_MSG_HOST_SLEEP(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

struct ipc_mem_msg_host_sleep β€” message structure for the sleep message. Okay bestie, welcome to the Kernel API Manual, specifically the page for struct ipc_mem_msg_host_sleep(9). This is the whole blueprint for that sleep-message situation, and we are gonna read it together like it’s the group chat. ✨

✨ SYNOPSIS ✨

Here’s the struct in all its structured glory, no cap β€” every field exactly as it appears:

       struct ipc_mem_msg_host_sleep {
           __le32 reserved1[2];
           u8 target;
           u8 state;
           u8 reserved2;
           u8 type_of_message;
           __le32 reserved3;
           __le32 reserved4;
           __le32 completion_status;
        };

It’s giving very β€œI have a place for everything and everything is in its place.” πŸ’…

πŸŽ€ Members πŸŽ€

  • reserved1 β€” Reserved. That’s literally the note, bestie β€” we don’t invent lore for reserved fields. πŸ™ˆ
  • target β€” 0 = host, 1 = device, and host or EP devie is the message target.
  • state β€” 0 = enter sleep, 1 = exit sleep, 2 = enter sleep no protocol.
  • reserved2 β€” Reserved.
  • type_of_message β€” Message type.
  • reserved3 β€” Reserved.
  • reserved4 β€” Reserved.
  • completion_status β€” Message Completion Status.

🌈 SEE ALSO 🌈

Lowkey the β€œread more” section, and we are keeping every single reference. The page points you at these:


xoxo, bestie β€” this page came from the ./drivers/net/wwan/iosm source and is dated October 2026. Go forth and struct responsibly. πŸ’…πŸ«Ά

πŸ“¦ where this page comes from