doc_probe_device(9)

📦 version 7.3.1, in nixpkgs unstable

💅 doc_probe_device(9) — like, the whole vibe check for a device ✨

okay so bestie, welcome to the Kernel API Manual entry for doc_probe_device 🎀 this one lives in section 9 (that's the kernel-functions girlies) and honestly? it's giving "small function, big feelings" 💖

🌸 NAME 🌸

doc_probe_device — check if a device is actually available, no cap 🕵️‍♀️

✨ SYNOPSIS ✨

struct mtd_info * doc_probe_device (struct docg3_cascade *cascade , int
floor , struct device *dev );

like literally that's the whole signature, she's not complicated 💅

🦋 ARGUMENTS 🦋

  • cascade — the cascade of chips that this device (or these devices, plural energy 🫶) is gonna belong to
  • floor — the floor of the device we're probing, ikr, floors, in my kernel? more likely than you think 😭
  • dev — the device itself, the main character 👑

💜 DESCRIPTION 💜

So what does she do? She checks whether a device at the specified IO range — and at that floor — is available. Simple as that, periodt 🌈

Here's the return-value tea ☕:

  • you get a mtd_info struct back if there is a device — slay 💅
  • you get ENODEV if none was found — not me getting rejected 😭
  • you get ENOMEM if a memory allocation failed — tragic, but it happens 🙈
⚠️ heads up bestie: if floor 0 is the one being checked, a reset of the ASIC gets launched. so like, know that before you poke it, fr fr 🔥

🔥 SEE ALSO 🔥

The kernel file to go read is ./drivers/mtd/devices/docg3.c — that's the mothership 🏠 and here's the whole friend group, no one gets left behind, iykyk:

and that's the whole page, bestie, you ate that 🍓 this lil beauty ships out of ./drivers/mtd/devices, dated October 2026, and she answers to the name doc_probe_device(9) 💖✨🫶

📦 where this page comes from