kempld_get_info(9)

📦 version 7.3.1, in nixpkgs unstable

💅 kempld_get_info(9) — Kernel API Manual, but make it make sense ✨

Okay bestie, so this is a page from the Kernel API Manual and honestly? It's short, it's sweet, and the function name is kempld_get_info. That (9) at the end? That's just the section number, iykyk. 🎀

✨ NAME ✨

kempld_get_info — update device specific information 🦋

✨ SYNOPSIS ✨

int kempld_get_info (struct kempld_device_data *pld );

No cap, that's the whole signature. It returns an int, and it takes one pointer. That's her. 💅

✨ ARGUMENTS ✨

  • pld — a struct kempld_device_data that describes the PLD. She's the main character here, the whole data situation lives in her. 👑

✨ DESCRIPTION ✨

So here's the tea, bestie: this function calls the configured board specific kempld_get_info_XXXX function. Notice the XXXX? That part is whatever the board is, not you. Don't try to pick it. 🙈

That board-specific function is the one actually responsible for gathering up all the information about the specific hardware. Literally its whole job. 🔍

And then? The information gets stored within the pld structure. So this function is giving very much "go fetch the hardware deets and drop them into pld" energy. Iconic. ✨

🫶 Quick vibe check so you don't forget: the info does not come from the generic side — it comes from whichever kempld_get_info_XXXX the board configured. Your code just calls, and the board-specific one does the gathering. Slay.

🌈 SEE ALSO 🌈

Kernel file ./drivers/mfd/kempld-core.c — yes, that's where she lives. Go look, fr fr. 💖

And the whole friend group she hangs out with:

Reads, writes, and the mutex pair — like, they come as a set, don't separate them. 😭

💜 That's the whole page, bestie. No filler, all facts, all ours. This beauty comes to you from ./drivers/mfd, dated October 2026, and it's kempld_get_info(9) all day. Go forth and update some device specific information. 🎀🦋🔥

📦 where this page comes from