STRUCT PANTHOR_PWR(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

struct panthor_pwr β€” bestie, this is the PWR_CONTROL block management data struct, and yes it's as iconic as it sounds ✨ (we're chilling in the Kernel API Manual today, iykyk)


✨ SYNOPSIS ✨

struct panthor_pwr {
    void __iomem *iomem;
    struct panthor_irq irq;
    spinlock_t reqs_lock;
    u32 pending_reqs;
    wait_queue_head_t reqs_acked;
 };

πŸŽ€ Members πŸŽ€

Okay so let's meet the cast, because every single one of these little fields is a main character in their own right πŸ’…

  • iomem β€” the CPU mapping of the PWR_CONTROL iomem region. basically the VIP pass to the party 🫢
  • irq β€” the PWR irq. that's it, that's the whole vibe 🌸
  • reqs_lock β€” a lock that protects access to pending_reqs, because we do NOT let the requests get trampled, no cap πŸ”₯
  • pending_reqs β€” the pending PWR requests, just sitting there waiting for their moment πŸ‘‘
  • reqs_acked β€” the PWR request wait queue. literally where requests go to get acknowledged, periodt ⭐

πŸ¦‹ SEE ALSO πŸ¦‹

Go check out the kernel file ./drivers/gpu/drm/panthor/panthor_pwr.c plus these absolutely iconic functions: retract_domain(9), delegate_domain(9), and panthor_pwr_domain_force_off(9) β€” all linked and everything, you're welcome πŸ’œ


And that's the whole page, bestie 🧚 from ./drivers/gpu/drm/panthor, dated October 2026, signing off as struct panthor_pwr(9) πŸ’– slay! πŸŽ€

πŸ“¦ where this page comes from