IHIDEV(4)

📦
version 11.0 · 2 versions
, in nixpkgs unstable

💅 IHIDEV(4) — like, the whole vibe check 🦋

Okay bestie, so this is ihidev(4), straight out of the Kernel Interfaces Manual (that's section 4 if you're keeping score 📓). Buckle up, because this one's short but it's iconic ✨

✨ NAME ✨

ihidev — I2C Human Interface Device support 🫶

Like, the driver that handles your human-interface-device situation over I2C. Yes. That. 🎀

🌸 SYNOPSIS 🌸

ihidev* at iic?
ims*    at ihidev? reportid ?

Read it, memorise it, put it on your lock screen 💅

🦋 DESCRIPTION 🦋

So the ihidev driver handles all the Human Interface Devices that are attached via the I2C bus. All of them. Every single one. She's not picking favourites 💖

Here's the thing though — each HID device can have several components, right? Like, for example, a keyboard and a mouse, all living in the same device. Yeah. And those components use different report identifiers — which is literally just a byte — to distinguish which one the incoming data is actually coming from. One byte. That's the whole filing system. Ngl, kind of obsessed with how simple that is 😭

And the ihidev driver isn't out here doing the actual work herself, no ma'am. She has other drivers attached to her that handle particular kinds of devices, and ihidev only dispatches data to them based on the report id. She's the connector, the group chat admin, the one who forwards the message to the right bestie. Main character behaviour, honestly 👑

⭐ SEE ALSO ⭐

  • ims(4) — go read it, it's right there 🍓

🌈 HISTORY 🌈

The ihidev driver appeared in NetBSD 8.0. So she's been here a minute. Respect the elder 💜

Friendly reminder bestie: this page is dated October 5, 2019 and the source/version line says Debian — so when you're citing her, that's the era she's living in 📅

okay that's the whole page, go forth and interface with your humans, ily, bye 🧚‍♀️🎀💖

📦 where this page comes from