BUS_CHILD_LOCATION(9)

💖 BUS_CHILD_LOCATION(9) 💖

okay so this is from the Kernel Developer's Manual, and it's genuinely useful for finding where a child device lives on the bus. no cap, it's giving "location check" energy. ✨

🌸 NAME 🌸

BUS_CHILD_LOCATION — obtain the location of a child on the bus. literally that's the whole quest, bestie. 💅

✨ SYNOPSIS ✨

#include <sys/param.h>
#include <sys/bus.h>
#include <sys/sbuf.h>

void
BUS_CHILD_LOCATION(device_t dev, device_t child, struct sbuf *sb);

💖 DESCRIPTION 💖

The BUS_CHILD_LOCATION() method returns the location of the child device. That location is a series of key=value pairs. The string must be formatted as a space-separated list of key=value pairs.

Names may only contain alphanumeric characters, underscores ('_') and hyphens ('-'). Values can contain any non-whitespace characters. Values containing whitespace can be quoted with double quotes ('"'). Double quotes and backslashes in quoted values can be escaped with backslashes ('´).

The location is defined as a series of characteristics of the child device that can be used to locate that device independent of what drivers are attached. Typically, these are slot numbers, bus addresses, or some topology formation. Where possible, buses are encouraged to provide locations that are stable from boot to boot and when other devices are added or removed. A location is not dependent on the kind of device at that location.

🦋 SEE ALSO 🦋

• bus(9)
• device(9)

that's the whole page, bestie! it comes from Debian and is dated April 22, 2021 — BUS_CHILD_LOCATION(9) signing off. 💖✨🎀