ENUM STRUCT_DEVICE_FLAGS(9)

💖 NAME 💖

enum struct_device_flags — that's the enum, bestie, and this page is from the Kernel API Manual. It's all about the flags living inside struct device, no cap 🫶

🎀 SYNOPSIS 🎀

enum struct_device_flags {
    DEV_FLAG_READY_TO_PROBE ,
    DEV_FLAG_CAN_MATCH ,
    DEV_FLAG_DMA_IOMMU ,
    DEV_FLAG_DMA_SKIP_SYNC ,
    DEV_FLAG_DMA_OPS_BYPASS ,
    DEV_FLAG_STATE_SYNCED ,
    DEV_FLAG_DMA_COHERENT ,
    DEV_FLAG_OF_NODE_REUSED ,
    DEV_FLAG_OFFLINE_DISABLED ,
    DEV_FLAG_OFFLINE ,
    DEV_FLAG_COUNT

};

✨ Constants ✨

Okay so here's the whole flag lineup, and yes, every single one is iconic in its own way 💅

• DEV_FLAG_READY_TO_PROBE — if this one's set, then device_add has finished enough initialization that probe could be called. It's giving "ready, set, probe" energy ✨
• DEV_FLAG_CAN_MATCH — the device has matched with a driver at least once, or it's in a bus (like AMBA) which can't check for matching drivers until other devices probe successfully. Lowkey a matchmaker flag 🎀
• DEV_FLAG_DMA_IOMMU — the device is using the default IOMMU implementation for DMA and doesn't rely on the dma_ops structure. Very "I got my own setup, thanks" 💅
• DEV_FLAG_DMA_SKIP_SYNC — DMA sync operations can be skipped for coherent buffers. Skipping the sync, not the vibes 🦋
• DEV_FLAG_DMA_OPS_BYPASS — if set, then the dma_ops are bypassed for the streaming DMA operations (->map_* / ->unmap_* / ->sync_*), and optional (if the coherent mask is large enough) also for dma allocations. This flag is managed by the dma ops instance from ->dma_supported. Big main-character energy for the bypass 😤
• DEV_FLAG_STATE_SYNCED — the hardware state of this device has been synced to match the software state of this device by calling the driver/bus sync_state callback. Synced and slaying 💫
• DEV_FLAG_DMA_COHERENT — this particular device is dma coherent, even if the architecture supports non-coherent devices. It's special like that 💖
• DEV_FLAG_OF_NODE_REUSED — set if the device-tree node is shared with an ancestor device. Family tree but make it kernel 🌳
• DEV_FLAG_OFFLINE_DISABLED — if set, the device is permanently online. Never offline, not even for a vibe check 🔥
• DEV_FLAG_OFFLINE — set after successful invocation of bus type's .offline. Bye bestie, you're offline now 😭
• DEV_FLAG_COUNT — number of defined struct_device_flags. The final boss of the enum count 👑

💫 Description 💫

Each flag should have a set of accessor functions created via __create_dev_flag_accessors for each access. Like, every flag gets its accessor treatment, okay? Periodt 💅

🔥 SEE ALSO 🔥

Kernel file ./include/linux/device.h is the home base, and here's the whole squad of references:

• struct subsys_interface(9)
• struct device_attribute(9)
• struct dev_ext_attribute(9)
• DEVICE_ATTR(9)
• DEVICE_ATTR_RW(9)
• DEVICE_ATTR_ADMIN_RW(9)
• DEVICE_ATTR_RW_NAMED(9)
• DEVICE_ATTR_RO(9)
• DEVICE_ATTR_ADMIN_RO(9)
• DEVICE_ATTR_RO_NAMED(9)
• DEVICE_ATTR_WO(9)
• DEVICE_ATTR_WO_NAMED(9)
• DEVICE_ULONG_ATTR(9)
• DEVICE_INT_ATTR(9)
• DEVICE_BOOL_ATTR(9)
• DEVICE_STRING_ATTR_RO(9)
• enum device_link_state(9)
• enum dl_dev_state(9)
• enum device_removable(9)
• struct dev_links_info(9)
• struct dev_msi_info(9)
• enum device_physical_location_panel(9)
• enum device_physical_location_vertical_position(9)
• enum device_physical_location_horizontal_position(9)
• struct device_physical_location(9)
• struct device(9)
• struct device_link(9)
• device_set_driver_override(9)
• device_has_driver_override(9)
• device_match_driver_override(9)
• device_iommu_mapped(9)
• dev_name(9)
• dev_bus_name(9)
• device_find_child_by_name(9)
• device_find_any_child(9)
• device_lock_set_class(9)
• device_lock_reset_class(9)

Source/version check: this page is from ./include/linux, dated October 2026, and its manual name is enum struct_device_flags(9). Now go forth and flag responsibly, bestie 💅✨