DEVICE_QUIET(9)

💖 DEVICE_QUIET(9) 💖

okay bestie, so this one lives in the Kernel Developer's Manual (section 9, kernel land, very demure, very mindful) and it's literally all about making a device shut up. yes. that's the whole vibe. let's get into it 🫶

---

✨ NAME ✨

device_quiet, device_verbose, device_is_quiet — manipulate the device quiet flag 💅

🌸 SYNOPSIS 🌸

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

void
device_quiet(device_t dev);

void
device_verbose(device_t dev);

int
device_is_quiet(device_t dev);

🦋 DESCRIPTION 🦋

so every single device has a quiet flag attached to it, right? like, its own little mood indicator. and when a device is created it's verbose by default — main character energy, wants everyone to know it's there. but you can quiet it, and quieting it does two things: it stops the device identification string from printing during attach, and it stops a message from printing during detach. so it just kind of… exists. silently. iconique.

the way you quiet a device is you call device_quiet() during a device driver probe routine. that's the moment. that's the window. 🎀

and if you ever want the probe messages back — to re-enable them — you call device_verbose(). un-mute. bring the volume back up. slay.

and to test whether a device is quieted (no assumptions, bestie, we check), you call device_is_quiet().

⚠️ heads up: devices are implicitly marked verbose after a driver detaches. so the quiet doesn't stick around forever — it resets on detach. not me finding that out the hard way 😭

🔥 SEE ALSO 🔥

• device(9)

👑 AUTHORS 👑

This manual page was written by Doug Rabson. we stan. 💜

---

okay that's the whole page, no notes, go forth and quiet your devices responsibly 🌈⭐

Debian · September 12, 2016 · mwah, that's a wrap, ty for reading bestie 🍓🧚