atc260x_device_probe(9)

💖 atc260x_device_probe(9) 💖

okay so this is a page from the Kernel API Manual and honestly? it's a little shortie but she's important. bestie, we're talking about atc260x_device_probe — the function that probes a configured ATC260x device. that's the whole vibe. let's get into it 🎀

---

✨ SYNOPSIS ✨

int atc260x_device_probe (struct atc260x *atc260x );

like, it takes one thing and gives you back an int. no cap. 💅

---

🫶 ARGUMENTS 🫶

• atc260x — the ATC260x device you want to probe. and bb, it must be configured already. this is not a "we'll figure it out later" situation, this is a "have your life together first" situation. 🙈

---

🌸 DESCRIPTION 🌸

so here's what's tea: this function is the moment where the ATC260x core goes ahead and registers the ATC260x MFD devices and the IRQCHIP. that's literally her job. that's the whole assignment. 👑

but — and this is the part where you need to pay attention — the ATC260x device you pass in must be fully configured. and by fully we mean:

• it's been set up with atc260x_match_device
• its IRQ is set
• its regmap is created

⚠️ no skipping steps, bestie. if you roll up with a half-configured device, that's not a vibe check you're gonna pass. the description says it must be fully configured, so... it must. periodt. 💀

get all three of those done first and she'll slay, registering the MFD devices and IRQCHIP exactly like she's supposed to. 🦋

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/mfd/atc260x-core.c — go read the source, iykyk 📖
• atc260x_match_device(9) — the pre-req bestie who does the matching ✨

---

and that's the page!! 🌈 this little cutie lives in ./drivers/mfd and the version/date on the door says October 2026 — so yeah, that's the source location, that's the date, we're all caught up. mwah, go probe something responsibly 💜💖🎀