dev_driver_string(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– dev_driver_string β€” Kernel API Manual πŸ’–

okay bestie, gather ’round, because this page is short and sweet and literally about finding out what driver a device is vibing with 🫢

🌸 NAME 🌸

  • dev_driver_string β€” return a device’s driver name, if at all possible ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

here’s the signature, exactly as it appears, no cap:

const char * dev_driver_string (const struct device *dev );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the struct device to get the name of πŸ“

πŸ’… DESCRIPTION πŸ’…

So here’s the tea β˜•: it will return the device’s driver’s name if it is bound to a device.

If the device is not bound to a driver, it will return the name of the bus it is attached to 🚌 β€” lowkey iconic fallback energy.

And if it is not attached to a bus either? You get an empty string, bestie β€” literally "" πŸ™ˆπŸ’€

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/base/core.c β€” and then the whole extended friend group:


mwah πŸ’‹ β€” this page’s source/version is ./drivers/base, dated October 2026; title stays dev_driver_string(9). byeee 🫢✨

πŸ“¦ where this page comes from