STRUCT RPMSG_EPTDEV(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct rpmsg_eptdev(9) ✨

okay so bestie, we're in the Kernel API Manual today and this one is literally the glow-up of a struct you're gonna meet in ./drivers/rpmsg/rpmsg_char.c β€” it's called struct rpmsg_eptdev, and it's basically the endpoint device context πŸŽ€ like, it holds the whole vibe of one rpmsg endpoint device. no cap. πŸ’…


🌸 SYNOPSIS 🌸

here's the whole squad, exactly as it appears, don't @ me:

struct rpmsg_eptdev {
    struct device dev;
    struct cdev cdev;
    struct rpmsg_device *rpdev;
    struct rpmsg_channel_info chinfo;
    struct mutex ept_lock;
    struct rpmsg_endpoint *ept;
    struct rpmsg_endpoint *default_ept;
    spinlock_t queue_lock;
    struct sk_buff_head queue;
    wait_queue_head_t readq;
    bool remote_flow_restricted;
    bool remote_flow_updated;
 };

πŸ’œ Members πŸ’œ

  • dev β€” the endpoint device itself. the main character πŸ’«
  • cdev β€” the cdev for the endpoint device. yes queen, char device representation ✨
  • rpdev β€” the underlaying rpmsg device. (their spelling, not mine, keeping it 100% exact fr fr) 🫢
  • chinfo β€” the info used to open the endpoint. like the lil guest list πŸ“‹
  • ept_lock β€” synchronization of ept modifications. keeps everyone from touching ept at the same time, iconic πŸ”’
  • ept β€” rpmsg endpoint reference, when open. note the when open β€” she's conditional πŸ¦‹
  • default_ept β€” set to channel default endpoint if the default endpoint should be re-used on device open to prevent endpoint address update. iykyk, this one's doing the quiet important work πŸ‘‘
  • queue_lock β€” synchronization of queue operations. another lock, another slay πŸ”
  • queue β€” incoming message queue. the inbox, but make it kernel 🌸
  • readq β€” wait object for incoming queue. she waits, patiently, dramatically 😭
  • remote_flow_restricted β€” to indicate if the remote has requested for flow to be limited. the remote said "chill please" 🧊
  • remote_flow_updated β€” to indicate if the flow control has been requested. basically the "did someone ask tho" flag πŸ™ˆ

πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./drivers/rpmsg/rpmsg_char.c β€” go read her, she's the whole reason this struct exists bestie πŸ’–

πŸ’€ quick vibe check: every field above is listed exactly as the kernel declares it β€” don't rename anything, the compiler will absolutely notice and it will not be slay.

✨ and that's the page! ✨ this cutie came from ./drivers/rpmsg, dated October 2026, and she's filed under struct rpmsg_eptdev(9) in the Kernel API Manual β€” go forth and be iconic with your endpoints, bestie πŸŽ€πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from