BUS_CHILD_PNPINFO(9)

🌸 NAME 🌸

BUS_CHILD_PNPINFO — obtain the plug and play information from a device. This one's from the Kernel Developer's Manual, bestie: the BUS_CHILD_PNPINFO(9) page is here to hand you the child device's pnp tea. 💅

✨ SYNOPSIS ✨

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

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

🦋 DESCRIPTION 🦋

Okay so bestie, the page says the BUS_CHILD_LOCATION() method returns the identifying information about the child device. (Not me noticing it says BUS_CHILD_LOCATION() and not BUS_CHILD_PNPINFO() — I'm keeping it exactly as written, no cap. 🙈)

Some buses call this identifying info the plug and play (pnp) details, and it's literally 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 — yes, any, iykyk. Values containing whitespace can be quoted with double quotes ("). Double quotes and backslashes in quoted values can be escaped with backslashes ('´').

The pnpinfo is defined as a series of characteristics of the child device that are independent of which drivers are attached, but are used to allow drivers to claim a device. Typically, plug and play information encodes who made the device, what the model number is, and some generic details about the device — iconic. By convention, only the generic information about the device that's used by drivers on that bus to decide on accepting the device is reported. Other configuration information (such as the cache burst size) needed for the operation of the device, but that doesn't distinguish it broadly from other devices, is not reported. Periodt. 💖

👑 SEE ALSO 👑

• bus(9)
• device(9)

xoxo, your Debian girlie 💅 — April 22, 2021 🌈. Source/version: Debian; page: BUS_CHILD_PNPINFO(9).