cs_slot_prog_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cs_slot_prog_locked(9)

okay bestie, welcome to the kernel API manual for cs_slot_prog_locked(9) β€” yes the name is a mouthful, yes it's iconic, and yes we're gonna get through it together 🫢


✨ NAME ✨

cs_slot_prog_locked β€” program a queue slot, literally what it says on the tin πŸ’–


🌸 SYNOPSIS 🌸

void cs_slot_prog_locked (struct panthor_device *ptdev , u32 csg_id ,
u32 cs_id );

that's it, that's the whole call. no return value, no drama, just vibes ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • ptdev β€” the Device. the whole struct panthor_device, your main character 🫢
  • csg_id β€” Group slot ID. the group's little slot number, iykyk
  • cs_id β€” Queue slot ID. the queue's own slot number, not to be confused with the group one (do not mix them up bestie, the scheduler can tell πŸ’€)

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so picture this: you've got a queue slot just sitting there doing nothing, and we're about to program it πŸ“ β€” like, we hand it all the queue information it needs so things can actually start being executed on this queue. the queue goes from "existing" to "girl, do something" ✨

πŸ’œ heads up though: the group slot must have a group bound to it already β€” that's what group_bind_locked is for. no group bound? no programming. periodt.

πŸ”₯ SEE ALSO πŸ”₯

everything lives in the kernel file ./drivers/gpu/drm/panthor/panthor_sched.c β€” go read it, it's giving main character energy πŸ‘‘


okay that's the whole page, you ate that πŸ’… one last thing β€” this gem comes to you from ./drivers/gpu/drm/panthor, dated October 2026, and it's filed under the manual name cs_slot_prog_locked(9). slay, go program a queue bestie 🌈⭐

πŸ“¦ where this page comes from