dev_bus_name(9)
okay so bestie, this is dev_bus_name(9) from the Kernel API Manual β it's giving tiny-helper-that-knows-your-device's-whole-bus/class-lore energy. πβ¨
β¨ NAME β¨
dev_bus_name β Return a device's bus/class name, if at all possible. π
π¦ SYNOPSIS π¦
const char * dev_bus_name (const struct device *dev );
π ARGUMENTS π
devβ thestruct deviceto get the bus/class name of. That's the whole assignment, bestie. π«Ά
πΈ DESCRIPTION πΈ
The way that this works is: it will return the name of the bus/class the device is attached to. If it is not attached to a bus/class, an empty string will be returned. No cap β that's literally the whole vibe. π
π₯ SEE ALSO π₯
Kernel file ./include/linux/device.h says hiii, and it brought the whole friend group:
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)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)device_find_child_by_name(9)device_find_any_child(9)device_lock_set_class(9)device_lock_reset_class(9)
Catch you later, bestie β this page came from ./include/linux, dated October 2026, and it's dev_bus_name(9) forever. Byeee! π¦ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms