STRUCT DEVICE_PHYSICAL_LOCATION(9)

🫶 struct device_physical_location(9) 🫶

okay so bestie, this page lives in the Kernel API Manual (yes, the page name shows up truncated as struct devi...cal_location(9) in the corner, that's just how it prints, don't stress 💅) and it's literally just a lil struct that holds all the info about where a device physically plugs into your machine. like, physically physically. the actual spot on the housing. no cap 🎀

---

✨ NAME ✨

struct device_physical_location — Device data related to physical location of the device connection point. 💖

like it's giving "where does this thing actually live on the box", and that's the whole vibe.

---

🌸 SYNOPSIS 🌸

struct device_physical_location {
    enum device_physical_location_panel panel;
    enum device_physical_location_vertical_position vertical_position;
    enum device_physical_location_horizontal_position
horizontal_position;
    bool dock;
    bool lid;
 };

that horizontal_position line wrapping is exactly how it's written, i'm not touching it, it's iconic ✨

---

🦋 Members 🦋

okay so here's the cast of characters, one by one:

• panel — Panel surface of the system's housing that the device connection point resides on. 🧚 like, which face of the chassis we talkin' about.
• vertical_position — Vertical position of the device connection point within the panel. ⬆️⬇️ where it sits up-and-down inside that panel.
• horizontal_position — Horizontal position of the device connection point within the panel. ⬅️➡️ and where it sits side-to-side, same panel.
• dock — Set if the device connection point resides in a docking station or port replicator. 🔌 so basically: is this a dock thing, yes/no.
• lid — Set if this device connection point resides on the lid of laptop system. 💻✨ like it's literally on the lid, slay.

ngl the dock and lid ones are bools so they're just "set" or "not set" — no in-between, periodt 💅

---

👑 SEE ALSO 👑

lowkey this is the part where the page just goes absolutely feral and names basically the entire device subsystem, bestie. buckle up. 🌈

Kernel file ./include/linux — and then, in the original order, fr fr:

• 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)
• enum struct_device_flags(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)

okay that's the whole squad 😭💜 especially clock the three device_physical_location_* enums up there — those are literally the types behind the fields in this very struct, so go read those next if you wanna know the actual allowed values, iykyk 👑

---

reminder bestie: the page header says struct devi...cal_location(9) on both sides and Kernel API Manual in the middle, and the footer tucks the source file ./include/linux on the left with the date October 2026 in the middle — i'm folding all of that in right here so nothing gets lost 🫶

and that's the whole page!! source lives at ./include/linux, dated October 2026, filed under struct devi...cal_location(9) in the Kernel API Manual — mwah, go touch grass (or, like, a docking station) 🍓💖✨