ENUM MHI_DEVICE_TYPE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ enum mhi_device_type(9) β€” like, the Kernel API Manual, bestie ✨

okay so picture this: you're deep in the kernel, you're vibing in MHI land, and you need to know what kind of device you're looking at. That's it. That's the whole enum. It's a little two-constant situation and honestly? iconic. Lowkey a mood board of device types. πŸ’…


🌸 NAME 🌸

enum mhi_device_type β€” the device types, periodt. πŸŽ€


✨ SYNOPSIS ✨

enum mhi_device_type {
    MHI_DEVICE_XFER ,
    MHI_DEVICE_CONTROLLER

};

no cap, that's the whole thing. two constants, living their best life. 🫢


πŸ’– CONSTANTS πŸ’–

  • MHI_DEVICE_XFER β€” this one handles data transfer. it's the main character doing the actual work, moving the data, slaying. πŸ”₯
  • MHI_DEVICE_CONTROLLER β€” the control device. it's giving manager energy, running the show behind the scenes. πŸ‘‘

πŸ‘‘ SEE ALSO πŸ‘‘

bestie, the lore is DEEP. every one of these is a real one, iykyk:

Kernel file: ./include/linux/mhi.h

like, go read them all. or don't. i'm not your mom. but you should. πŸ’€


that's the whole page, babe β€” nothing hidden, no secret bonus constants, we keep it πŸ’― around here 🌈

kisses from the source tree πŸ’œ this one lives at ./include/linux, dated October 2026, and it's filed under enum mhi_device_type(9) in the Kernel API Manual β€” mwah, bye bestie! πŸ§šβ€β™€οΈπŸ“

πŸ“¦ where this page comes from