pcs_irq_chain_handler(9)

👑 pcs_irq_chain_handler(9) 👑

okay bestie, welcome to the Kernel API Manual page for pcs_irq_chain_handler(9) 💖 — yes, the manual name is folded right in here so we don't have to copy the whole header line like a boring PDF. This is the dedicated chained-interrupt handler page, and we're gonna get through it together. No cap. ✨

🌸 NAME 🌸

pcs_irq_chain_handler — handler for the dedicated chained interrupt case. That's the name, and it ate. 💅

✨ SYNOPSIS ✨

void pcs_irq_chain_handler (struct irq_desc *desc );

🎀 ARGUMENTS 🎀

• desc — interrupt descriptor. That's the whole argument list, bestie, and she's carrying the interrupt descriptor energy. 🫶

🦋 DESCRIPTION 🦋

okay so literally the description is: use this if you have a separate interrupt for each pinctrl-single instance. That's the entire assignment. No extra lore, no secret side quest, just that. 😭✨

bestie this is the dedicated chained interrupt case — if that's your setup, this is your handler. periodt. 💅

🌈 SEE ALSO 🌈

Kernel file ./drivers/pinctrl/pinctrl-single.c — and then the whole cast, in order, no skipping:

• struct pcs_func_vals(9)
• struct pcs_conf_vals(9)
• struct pcs_conf_type(9)
• struct pcs_function(9)
• struct pcs_gpiofunc_range(9)
• struct pcs_data(9)
• struct pcs_soc_data(9)
• struct pcs_device(9)
• pcs_add_pin(9)
• pcs_allocate_pin_table(9)
• pcs_add_function(9)
• pcs_get_pin_by_offset(9)
• pcs_parse_one_pinctrl_entry(9)
• pcs_dt_node_to_map(9)
• pcs_irq_free(9)
• pcs_free_resources(9)
• struct pcs_interrupt(9)
• pcs_irq_set(9)
• pcs_irq_mask(9)
• pcs_irq_unmask(9)
• pcs_irq_set_wake(9)
• pcs_irq_handle(9)
• pcs_irq_handler(9)
• pcs_irq_init_chained_handler(9)
• pcs_quirk_missing_pinctrl_cells(9)

okay that's the page, bestie 💖 cute little footer tea: this is pcs_irq_chain_handler(9) from the Kernel API Manual, source/version vibes come from ./drivers/pinctrl, and the date is October 2026. Mwah, bye. 🎀