DEVICE_QUIET(9)

πŸ’– DEVICE_QUIET πŸ’–

okay bestie, welcome to DEVICE_QUIET(9) from the Kernel Developer's Manual β€” this is the page about making devices stop yapping in your dmesg. yes, it's real, and yes, it's iconic.


✨ NAME ✨

device_quiet, device_verbose, device_is_quiet β€” manipulate 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);

like, copy that exactly, do not freestyle the includes, i am begging 🫢


πŸ¦‹ DESCRIPTION πŸ¦‹

so. every single device has a quiet flag attached to it. that's the whole vibe. πŸ’…

a device is verbose by default when it is created β€” main character energy, it wants to be seen, it wants to be heard β€” but you can quiet it, which prevents:

  • printing of the device identification string during attach, and
  • printing of a message during detach.

to quiet a device, call device_quiet() during a device driver probe routine. that's the moment, that's the window, that's when you do it. ✨

to re-enable probe messages, call device_verbose(). it's the undo button, it's giving second chances. πŸ™ˆ

to test to see if a device is quieted, call device_is_quiet() β€” she will tell you the truth, no cap. πŸ”₯

oh and heads up: devices are implicitly marked verbose after a driver detaches. so the quiet doesn't last forever, bestie. the system just does that on its own. periodt.

πŸ‘‘ SEE ALSO πŸ‘‘


πŸ’œ AUTHORS πŸ’œ

this manual page was written by Doug Rabson. king behaviour honestly. πŸ‘‘


that's the whole page, you ate it. this one came from the Debian crew and it's dated September 12, 2016 β€” old but still slaying fr fr πŸ’–πŸŒΈβœ¨

πŸ“¦ where this page comes from