qcom_pdc_gic_set_type(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qcom_pdc_gic_set_type(9) β€” like, the Kernel API Manual page bestie πŸ’…

okay so this is a page straight outta the Kernel API Manual, and it's literally about telling the PDC how to handle your interrupt. no cap, it's a whole mood. πŸŽ€


✨ NAME ✨

qcom_pdc_gic_set_type β€” configure the PDC for the interrupt πŸ¦‹

✨ SYNOPSIS ✨

int qcom_pdc_gic_set_type (struct irq_data *d , unsigned int type );

✨ ARGUMENTS ✨

  • d β€” the interrupt data. iconic. it's the irq_data, the whole main character of the call. πŸ‘‘
  • type β€” the interrupt type. yeah. that's the vibe check we're doing. πŸ’…

✨ DESCRIPTION ✨

okay so here's the tea πŸ“: if type is edge triggered, this function forwards that as a rising edge, because the PDC takes care of converting all edge types to a rising edge signal. literally all of them. not me being obsessed with the PDC's commitment to the rising edge aesthetic πŸ’€βœ¨

and if type is level, then it forwards that as level high, because β€” you guessed it β€” the PDC takes care of converting all level types to a level high signal. it's giving "the PDC handles the conversion, you just tell it edge or level." periodt. 🌸

so fr fr: edge in β†’ rising edge out, level in β†’ level high out. that's the whole conversion arc and the PDC is the one slaying it, not you. 🫢

✨ SEE ALSO ✨

  • the Kernel file ./drivers/irqchip/qcom-pdc.c β€” go read it iykyk πŸ“–
  • struct pdc_regs(9)
  • struct pdc_irq_cfg(9)
  • struct pdc_desc(9)
  • qcom_pdc_gic_secondary_set_type(9)

🌈 that's the whole page bestie, no notes, ate and left no crumbs. this one's comin' at you from the ./drivers/irqchip source, dated October 2026 β€” yeah, the future. πŸ’œπŸ’–βœ¨

πŸ“¦ where this page comes from