Open Source: Our Work in the Mainline Linux Kernel

We write drivers to be merged in the mainline Linux kernel, not to sit in a vendor tree. Every change listed on this page is in Linus Torvalds’ tree.

Most of our recent upstream work brought the Renesas RZ/G3E SoC to mainline Linux, from the clock tree to audio and PCIe, and fixed bugs found along the way in other drivers. The full list of our commits is on kernel.org.

Our Contributions

Audio (ASoC)

RZ/G3E support in the Renesas sound driver, rsnd: SoC probing and register map, DMA addresses, resets of the SSI, SRC and ADG blocks, per-SSI clock management, shared SCU clocks, and system suspend and resume. The device tree binding and the board’s DA7212 codec came with it.

PCI Express

RZ/G3E support in the RZ/G3S PCIe host driver: SoC-specific callbacks and registers, a reworked inbound window algorithm, PCIe Gen3 at 8 GT/s, and fixes to reset handling in the probe error path and during suspend.

Clocks, SoC and DMA

RZ/G3E clocks and resets for audio, Ethernet, PCIe and the thermal unit, the RZ/V2H clock driver moved to the clk_hw API, RZ/G3E support with syscon access in the system controller driver, and DMA acknowledge routing between the DMA controller and the interrupt controller.

Thermal

The thermal driver for the RZ/G3E temperature sensor unit, with its device tree binding, and its follow-up fixes.

Device Trees

The RZ/G3E SoC and its SMARC board: Gigabit Ethernet, PCIe and its reference clock, sound, the RAA215300 PMIC, the Versa3 clock generator and the I2C buses.

Fixes in Other Drivers

Bugs found while working on other platforms: a use-after-free and a precedence error in the i.MX SPI driver, the wrong interrupt register read in the Rockchip SPI driver, an unbalanced wake-up interrupt in the ISL1208 RTC driver, and clean-ups in pin control.

Why We Work Upstream

A driver merged upstream is reviewed by the maintainers of its subsystem, tested by everyone who runs the kernel, and carried to every new release. A driver kept in a product tree has to be ported again at each kernel update, and its bugs are found by one team only. We apply the same approach to our clients’ platforms: when they agree, the drivers we write for them go upstream, and their product moves to new kernels without a fork to maintain.

Books and Training

What we learn upstream goes into our two books on Linux device drivers, Linux Device Driver Development and Mastering Linux Device Driver Development, published by Packt, and into our Linux device driver training.

Get Your Drivers Upstream

Need a driver for your hardware, or one merged in the mainline kernel? Tell us about it.