UI_GET_SYSNAME(9)

✨ UI_GET_SYSNAME 💅

okay so this one lives in the Kernel API Manual (yes bestie, the whole man page collection, we're in the big leagues now 🎀) and it's about finding out what sysfs decided to call your brand-new uinput device. let's get into it 🦋

---

🌸 NAME 🌸

UI_GET_SYSNAME — get the sysfs name of the created uinput device. that's it, that's the whole vibe. it tells you what your device got named 👑

---

⭐ SYNOPSIS ⭐

UI_GET_SYSNAME (len );

literally the entire call, no cap ✨

---

🎀 ARGUMENTS 🎀

• len — okay so the source literally just says -- undescribed -- for this one 💀 not me being lazy, that's genuinely all the documentation gives us. so: it's the length, and that's all we know for sure 🙈

---

🔥 DESCRIPTION 🔥

so you made a virtual input device, iconic, and now you wanna know what sysfs is calling it? this is the function that returns the sysfs name of the created virtual input device. slay.

the complete sysfs path is then:

/sys/devices/virtual/input/--NAME--

where that --NAME-- is the name you got back 🫶 and usually, it's in the form "inputN" — like input0, input1, whatever number the kernel felt like handing out that day. iykyk 💫

no cap: "usually" is doing a lot of work in that sentence — the kernel is telling you it's typically inputN, not swearing a blood oath that it always will be 🌈

---

💜 SEE ALSO 💜

• kernel file ./include/uapi/linux/uinput.h — the header where all the uinput goodies live 📁
• UI_DEV_SETUP(9)
• UI_ABS_SETUP(9)
• UI_GET_VERSION(9)

go read those next bestie, they're all part of the same lil uinput friend group 👯‍♀️

---

and that's the whole page!! 💖 this one's from the source tree at ./include/uapi/linux, dated October 2026, and it was rendered in the Kernel API Manual — go off, sysfs namer 🧚✨💅