Whack-a-Mole with DTS Validation in the Linux Kernel
summary
Maintains and measures DT validation across kernels 5.3–6.8 using the DTC compiler and the DT schema Python package, analyzing ~3,500 DTS-related commits and ~2,500 commits for arm64 Qualcomm; Samsung Exynos reaches full schema compliance, Qualcomm grows to ~236 boards and still averages ~8 DTC/DT-schema warnings per arm64 target. Findings: ~50% of flagged items are style noise, ~30% harmless improvements, ~10% possible portability fixes and ~10% real bugs; converting text bindings to YAML reduces noise.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:23What is Device Tree and DTS
- 3:37Why validating DT bindings matters
- 5:25Measuring validation warnings
- 7:28Platforms and configurations tested
- 9:16Growth of DT targets over time
- 10:20Types of DT validation warnings
- 12:31DTS validation explained
- 16:23Whack-a-Mole analogy
- 23:04Classifying warning fixes
- 26:16Results of warning analysis
- 30:25Conclusion and future
- 31:06Q&A
- 31:27DT Schema and YAML files
- 31:50Schema updates and drivers
- 32:30Automated validation in checkpatch
- 33:54Overlay compilation with symbols
- 34:59Vendor schema diligence
- 36:22Enabling DT Schema in checkpatch
- 38:28Advice for new contributors
- 40:12Automating DT Schema with GitHub
- 42:18DT Schema support in U-Boot
- 44:48Cross-OS DT adoption
related talks
33mDPDK CI Testing Labs: New Tools, Lab Test Coverage, and DTS
18mTesting Intel TDX functionality with new set of self tests
34mLinux Kernel Testing: Providing Better Results to the Upstream Community
54mTDD for Microcontrollers
01h 00mMetal-In Test-Driven Development: A Dual-Target TDD approach
19mUpstream kernel CI using patchew and TDC
28mdbt-score: a linter for your dbt model metadata
38mHow we implemented TDD in Embedded C/C++