STRUCT WWAN_DEVICE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct wwan_device(9) β€” the Kernel API Manual, bestie edition ✨

Okay so like, hi, welcome to the struct wwan_device(9) page from the Kernel API Manual πŸŽ€ this is the ~iconic~ little struct that defines a WWAN device, and honestly she's giving main character energy. Let's get into it πŸ¦‹


✨ NAME ✨

struct wwan_device β€” the structure that defines a WWAN device πŸ’–


🌸 SYNOPSIS 🌸

struct wwan_device {
    unsigned int id;
    int refcount;
    struct device dev;
    const struct wwan_ops *ops;
    void *ops_ctxt;
  #ifdef CONFIG_WWAN_DEBUGFS;
    struct dentry *debugfs_dir;
  #endif;
 };

Like, that's the whole blueprint, bestie. Every field, exactly as it lives. No notes. Periodt. πŸ’…


πŸ‘‘ Members πŸ‘‘

  • id β€” the WWAN device's unique ID, like its very own username that nobody else can have πŸ”₯
  • refcount β€” the reference count of this WWAN device. The way that this works is: when this refcount reaches zero, the device gets deleted 😭 that's the whole lifecycle, no cap.
NB: access is protected by the global wwan_register_lock mutex. Like, do not touch it outside that lock, fr fr. Respect the mutex. πŸ™ˆ
  • dev β€” the underlying device underneath it all, the ~foundation~ of the vibe 🫢
  • ops β€” the wwan device ops. Yep. That's the ops. πŸ’œ
  • ops_ctxt β€” the context to pass to those ops. Little care package for the ops, iconic πŸŽ€
  • debugfs_dir β€” the WWAN device debugfs dir ✨ (this one only shows up when CONFIG_WWAN_DEBUGFS is defined, iykyk)

πŸ¦‹ SEE ALSO πŸ¦‹

Like, go read those next, they're literally the rest of the lore 🌈


aaaand that's the page, bestie πŸ’– this cutie lives over at ./drivers/net/wwan, stamped October 2026, and the page itself is struct wwan_device(9) β€” so next time someone asks, you already know. Slay πŸŒΈπŸ‘‘

πŸ“¦ where this page comes from