devm_sdca_irq_allocate(9)
π devm_sdca_irq_allocate β¨
okay bestie, welcome to the Kernel API Manual β this one's short and sweet and honestly kind of a vibe π
π¦ NAME π¦
devm_sdca_irq_allocate β literally just allocates an SDCA interrupt structure for a device. that's the whole job. no cap π
β¨ SYNOPSIS β¨
struct sdca_interrupt_info * devm_sdca_irq_allocate (struct device *sdev
, struct regmap *regmap , int irq );
look at her. three args, one pointer back, iconic behavior only π
πΈ ARGUMENTS πΈ
sdevβ the device pointer, and yes she's the one everything gets allocated against (devm energy β the cleanup is not your problem, bestie π«Ά).regmapβ theregmapused to poke at the SDCA IRQ registers. this is the access route, treat her right.irqβ the interrupt number. the actual number. the irq itself. fr fr π
π DESCRIPTION π
so the way this works: typically you'd call this from the top level driver for the whole SDCA device. why? because only a single instance is required across all Functions on the device. one. uno. that's the tea β β don't be out here allocating one per Function, that's not the move π
π RETURN π
a pointer to the allocated sdca_interrupt_info struct β or an error code π (so like, always check, bestie. always check.)
β SEE ALSO β
kernel file ./sound/soc/sdca/sdca_interrupts.c and the whole friend group:
sdca_irq_request(9)sdca_irq_free(9)sdca_irq_data_populate(9)sdca_irq_populate_early(9)sdca_irq_populate(9)sdca_irq_cleanup(9)sdca_irq_cleanup_late(9)sdca_irq_enable_early(9)sdca_irq_enable(9)sdca_irq_disable(9)
π quick vibe check: everything above is exactly as documented, no extra lore, no invented behavior. iykyk.
and that's the whole page π§ from the source ./sound/soc/sdca, dated October 2026 β mwah, go allocate something 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