What is the difference between a kernel driver and a user-space driver (UIO, spidev)?
Short answer: A kernel driver runs in kernel space, handles interrupts directly and plugs into a subsystem (network, input, IIO, DRM), so any application can use the device through a standard interface. A user-space driver talks to the hardware through a generic kernel helper (spidev, i2c-dev, UIO, VFIO, libgpiod); it is faster to write and debug and can stay proprietary, but it has higher latency, cannot be used by other kernel subsystems, and is harder to make safe.
| Kernel driver | User-space driver | |
|---|---|---|
| Interrupt latency | microseconds, top half runs immediately | scheduling latency of a process (tens of µs to ms) |
| Crash impact | can panic the whole system | only the process dies |
| Debugging | printk, ftrace, kgdb; reboot on mistakes | gdb, valgrind, normal tools |
| Integration | standard interfaces (/dev/input, net, iio, v4l2), used by any app and by other drivers |
custom API for your application |
| License | must be GPL-compatible to use GPL-only kernel symbols | can be proprietary |
| Maintenance | must track kernel API changes (unless upstreamed) | stable user-space ABI |
Generic helpers for user-space drivers
- spidev (
/dev/spidevB.C): full-duplex SPI transfers withioctl(SPI_IOC_MESSAGE). - i2c-dev (
/dev/i2c-N):ioctl(I2C_SLAVE, addr)thenread/write, orI2C_RDWRfor combined transactions. - UIO (
/dev/uioN):mmap()the device registers; a blockingread()returns when an interrupt arrives (the small kernel part only acknowledges/masks it). - VFIO: like UIO but with IOMMU protection so a user-space driver can do DMA safely (used by DPDK and for PCIe devices).
When to use which
- Prototype or bring-up: user space (quick to iterate).
- A sensor read once a second by one application:
i2c-dev/spidevis fine. - Anything other applications or subsystems need (network interface, input device, display, audio), anything with tight interrupt timing, or DMA without an IOMMU: write a kernel driver, and consider upstreaming it.
Follow-up: "spidev in the device tree?" Bind a specific compatible that the spidev driver lists (or use driver_override); a plain compatible = "spidev" is rejected because the device tree should describe hardware, not which driver to use.