phy_mdm6600_wakeirq_thread(9)

💖 NAME 💖

phy_mdm6600_wakeirq_thread — bestie, this is the function that handles the mode1 line OOB wake after booting ✨

So like, welcome to the Kernel API Manual entry for it — that's the manual name, and yes it's giving very much "I read kernel docs for fun" energy 🎀

---

✨ SYNOPSIS ✨

irqreturn_t phy_mdm6600_wakeirq_thread (int irq , void *data );

That's the whole signature, no cap. Returns an irqreturn_t, takes an int and a void *, iconic behavior honestly 💅

---

🌸 ARGUMENTS 🌸

• irq — this one's the interrupt 🫶 like, the actual interrupt number coming in.
• data — the interrupt handler data 💖 the lil payload that gets passed along to the handler.

---

🦋 DESCRIPTION 🦋

Okay so here's the lore 👑 GPIO mode1 starts its life as an output — it's used initially to configure the USB boot mode for mdm6600. Yeah. Before the boot, output. That's its job. Respect it 💅

After booting though?? Glow-up era ✨ it switches to being an input, and now it's catching the OOB wake signal coming from mdm6600 over to the SoC. Main character energy honestly 🌈

Ngl, for now it's just used for debug info only — like, it's not out here running the whole show yet, it's vibing in the debug lane 🙈 keep that in mind bestie.

---

🎀 SEE ALSO 🎀

Kernel file: ./drivers/phy/motorola/phy-mapphone-mdm6600.c — go read it, it's the source of truth fr fr 📖

And the whole friend group of related functions, all in their (9) era 💜:

• phy_mdm6600_cmd(9)
• phy_mdm6600_status(9)
• phy_mdm6600_init_irq(9)
• phy_mdm6600_init_lines(9)
• phy_mdm6600_device_power_on(9)
• phy_mdm6600_device_power_off(9)

---

So yeah, that's the whole page bestie 🍓 it lives over in ./drivers/phy/motorola and the manual's dated October 2026 ⭐ and that's the tea, mwah 💋🧚‍♀️