hwicap_get_...ion_register(9)

💅 hwicap_get_configuration_register(9)

okay so bestie, welcome to the Kernel API Manual ✨ this one's about hwicap_get_configuration_register and honestly? it's giving "small function, big job." let's get into it 🫶

---

🌸 NAME 🌸

hwicap_get_configuration_register — literally just queries a configuration register. that's the whole vibe check 💅

---

✨ SYNOPSIS ✨

int hwicap_get_configuration_register (struct hwicap_drvdata *drvdata ,
u32 reg , u32 *reg_data );

three args, one int coming back at you. slay.

---

🎀 ARGUMENTS 🎀

• drvdata — a pointer to the drvdata. iconic. it's the driver data, she's the main character here 👑
• reg — a constant that represents the configuration register value to be returned. so like, you tell it which register you want, and it goes and gets it 🔥
• reg_data — returns the value of the register. this is the output param, she's carrying the answer back to you 🦋

---

🍓 EXAMPLES 🍓

XHI_IDCODE, XHI_FLR.

(those are the ones the page shouts out, no cap 💖)

---

💫 RETURN 💫

soooo the original hits the RETURN heading and then just... moves straight on into the description. no return value deets listed here, bestie — that's just how the page is written 🙈

---

🌈 DESCRIPTION 🌈

So what does it actually do? It sends a query packet to the ICAP, and then it receives the response. that's the whole loop, simple as 🎀

and the important bit: the icap is left in Synched state. keep that in mind, iykyk ⭐

---

👑 SEE ALSO 👑

• Kernel file ./drivers/char/xilinx_hwicap/xilinx_hwicap.c — go read the source, it's literally right there 📖
• hwicap_command_desync(9) — the desync sibling, the other half of the story 🧚

---

okay that's the whole page!! go query those registers, you're gonna ate 💅✨

sign-off time: this little cutie lives in ./drivers/char/xilinx_hwicap, and the source/version stamp says October 2026 — so mark your calendars, bestie 💜🦋