STRUCT SG204X_MSI_CHIPDATA(9)
π struct sg204x_msi_chipdata(9) π
ok so bestie, welcome to the Kernel API Manual, section 9 β we're talking about struct sg204x_msi_chipdata, which is literally the chip data for the SG204x MSI IRQ controller. no cap, that's the whole vibe. π¦
β¨ NAME β¨
struct sg204x_msi_chipdata β chip data for the SG204x MSI IRQ controller. that's it, that's the queen. π
πΈ SYNOPSIS πΈ
struct sg204x_msi_chipdata {
void __iomem *reg_clr;
phys_addr_t doorbell_addr;
u32 irq_first;
u32 num_irqs;
unsigned int irq_type;
unsigned long *msi_map;
struct mutex msi_map_lock;
const struct sg204x_msi_chip_info *chip_info;
};
likeβ¦ look at her. every field accounted for, not one dropped. we love a complete struct. π«Ά
π Members π
reg_clrβ the clear reg, ok? go look at the TRM,10.1.33,GP_INTR0_CLR. iykyk πdoorbell_addrβ this one's the doorbell π, see the TRM,10.1.32,GP_INTR0_SET.irq_firstβ the first vectors number that MSIs starts. that's where the party begins β¨num_irqsβ number of vectors for MSIs. like, how many seats are at the table πΊirq_typeβ the IRQ type for MSIs. the whole personality of the interrupt, honestly πmsi_mapβ the mapping for allocated MSI vectors. ur lil map of who got which vector πΊοΈmsi_map_lockβ the lock formsi_map. yes bestie, we lock it, we do NOT rawdog shared state πchip_infoβ chip specific infomations. (that's the original spelling and i'm keeping it fr fr, no editing the source material π)
π SEE ALSO π
- Kernel file
./drivers/irqchip/irq-sg2042-msi.cβ go read it, it's giving main character energy π₯
ok that's the whole page, nothing skipped, nothing invented. if u use this struct wrong that's on u, not me π
sign-off time π β this was ./drivers/irqchip, dated October 2026, from the Kernel API Manual, and the page is literally called struct sg204x_msi_chipdata(9). slay, bye πβ¨
π¦ 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