ipa_probe(9)

💅 ipa_probe(9) — like, the actual manual page, bestie 🎀

okay so this is a page from the Kernel API Manual, and it's about ipa_probe — the IPA platform driver probe function. yes it's a mouthful, no we're not scared of it. let's go ✨

---

🌸 NAME 🌸

ipa_probe — the IPA platform driver probe function, aka the glow-up entry point for the whole IPA driver 👑

---

🦋 SYNOPSIS 🦋

int ipa_probe (struct platform_device *pdev );

literally that's it. one function, one job, main character energy fr 💅

---

🍓 ARGUMENTS 🍓

• pdev — platform device pointer. that's the plug, bestie 🔌

---

⭐ RETURN ⭐

• 0 if successful 🎉
• a negative error code if not 😭 — and yes, that error code might legitimately be EPROBE_DEFER, which is the "not yet, ask me again later" of the kernel world 🙈

---

🔥 DESCRIPTION 🔥

so this right here? this is the main entry point for the IPA driver. the front door. the bouncer at the club. and the initialization lowkey happens in several stages, in this exact order:

• the "init" stage — all the stuff that can be set up without touching the IPA hardware. no hardware access needed, it's giving prep work in your pajamas 🧚
• the "config" stage — this one does need IPA power to be active, because it reads and writes IPA registers. but ngl it does not need IPA immediate commands, so it's chiller than it sounds 💜
• the "setup" stage — this one uses IPA immediate commands, so it straight up requires the GSI layer to be initialized first. no GSI, no setup, periodt 💀

---

now, here's the fun part 🌈 a Boolean Device Tree property called modem-init decides who handles GSI initialization:

• AP (Trust Zone) does it, or
• the modem does it

if the AP does the GSI initialization, then the setup phase is entered only after that has completed successfully 🫶

if the modem does it instead, the modem initializes the GSI layer and then signals that it's finished by sending an SMP2P interrupt to the AP — and that is what triggers the start of IPA setup. iconic behavior, honestly ⚡

bestie please note: the modem-init property is what steers this whole flow, so don't be surprised when the setup phase kicks off from an interrupt instead of from your own code 🙈

---

👑 SEE ALSO 👑

• Kernel file ./drivers/net/ipa/ipa_main.c
• The IP Accelerator(9)
• enum ipa_firmware_loader(9)
• ipa_setup(9)
• ipa_teardown(9)
• ipa_hardware_dcd_config(9)
• ipa_hardware_config(9)
• ipa_hardware_deconfig(9)
• ipa_config(9)
• ipa_deconfig(9)

like, read them all, iykyk 📚💖

---

and that's the page!! 🌟 this lil beauty lives under ./drivers/net/ipa and it's dated October 2026, in case anyone asks — and it's still ipa_probe(9), always and forever 💫

mwah, go probe something 🫶🎀