rpmsg_chrdev_eptdev_create(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rpmsg_chrdev_eptdev_create(9) πŸ’…

okay bestie, welcome to the Kernel API Manual β€” this one's a little function with main character energy, and it lives in the kernel's rpmsg corner 🌸


✨ NAME ✨

rpmsg_chrdev_eptdev_create β€” registers a char device based on an endpoint, fr fr πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int rpmsg_chrdev_eptdev_create (struct rpmsg_device *rpdev , struct
       device *parent , struct rpmsg_channel_info chinfo );

like, look at her. three args, returns an int, no notes πŸ’…


πŸ“ ARGUMENTS πŸ“

  • rpdev β€” the prepared rpdev you're gonna use for creating endpoints. it's already prepped, bestie, don't come at it raw πŸ™ˆ
  • parent β€” the parent device. every icon needs a parent, iykyk πŸ‘‘
  • chinfo β€” the associated endpoint channel information. this is literally the blueprint for the endpoint 🧚

πŸ’– DESCRIPTION πŸ’–

so what does she do? this function creates a new rpmsg char endpoint device, which instantiates a fresh new endpoint based on whatever the chinfo information says 🌈

that's it. that's the whole vibe. she reads the chinfo, she makes the endpoint device, she slays ✨


πŸ”₯ SEE ALSO πŸ”₯


ngl, if you're creating endpoints you're gonna want to know how to destroy them too. balanced, like all things should be 🫢

okay that's the page!! source location is ./drivers/rpmsg, dated October 2026, and it's rpmsg_chrdev_eptdev_create(9) all the way down πŸŽ€βœ¨ mwah, go read the kernel, ily πŸ’œ

πŸ“¦ where this page comes from