STRUCT PANTHOR_PWR(9)
π 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_CONTROLiomemregion. 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 topending_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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms