usb_driver_claim_interface(9)

📦 version 7.3.1, in nixpkgs unstable

💅 usb_driver_claim_interface(9) — like, the Kernel API Manual entry you actually wanna read 🫶

okay bestie, so this is a page from the Kernel API Manual, and it's about binding a driver to an interface. yes, that kind of binding. sit down, hydrate, let's go ✨

🌸 NAME 🌸

usb_driver_claim_interface — bind a driver to an interface

like literally what it says on the tin, no cap 💖

✨ SYNOPSIS ✨

int usb_driver_claim_interface (struct usb_driver *driver , struct
usb_interface *iface , void *data );

three args, one int coming back at you, that's the whole vibe 🎀

🦋 ARGUMENTS 🦋

  • driver — the driver that's getting bound. it's the main character here, obviously 👑
  • iface — the interface it will be bound to. important detail bestie: this must be in the usb device's active configuration. if it's not, that's a whole situation 💀
  • data — the driver data associated with that interface. this is your stuff, do whatever, it's yours 🍓

💜 DESCRIPTION 💜

okay so here's the tea 🍵 — this function is for usb device drivers that need to claim more than one interface on a device when probing. like, greedy? no. necessary? yes. the current examples are audio and acm, so that's the energy we're working with 🔥

and listen — no device driver should directly modify internal usb_interface or usb_device structure members. none. not even a little. don't touch the internals, that's not your business, that's giving "i can fix him" energy and it never works 😭

⚠️ also, callers must own the device lock. yes, mandatory. locking discipline is not a suggestion, it's a lifestyle 💅

good news though: driver probe entries don't need extra locking because they already own it. but other call contexts? yeah, they may need to explicitly claim that lock. so check your context before you go touching things, iykyk 🙈

🌈 RETURN 🌈

0 on success. that's it. that's the whole return section. slay, honestly 💀

🧚 SEE ALSO 🧚

kernel file ./drivers/usb/core/driver.c, and the whole friend group:

that's the whole autopm cinematic universe fr fr 🌟

okay so that's the page!! and for legal reasons (and because it's cute) — this whole thing lives in ./drivers/usb/core, it's part of the Kernel API Manual, and it's dated October 2026 🎀 bye bestie, go own that device lock 💖✨

📦 where this page comes from