DT formatter - a maintainer's and contributor's elusive dream?
summary
A formatter that normalizes style aims to cut weeks of review churn by enforcing a common subset of DTS syntax and ordering rather than changing semantics; the tree of concern is ~3,000 DTS files with wildly differing styles, DTC’s existing -sort is inadequate, and reviewers want auto-correction & CI/IDE integration. Two prototypes exist (a Rust project with a CLI and VS Code language-server and a Python tokenizer/formatter) but neither is production-ready; a DTS-aware git-merge and binding checks are also proposed.
AI-written summary · about
chapters (7)
- 0:00Introduction and problem
- 3:10Current DT style issues
- 6:48Desired tool features
- 10:19Merge conflict detection
- 13:51Existing tool attempts
- 17:45Tool development status
- 20:37Next steps and Q&A
related talks
34mDTS 101: From Roots To Trees, Aka Devicetree for Beginners
33mStructured Documentation and Validation for Device Tree
36mHow to Get Your DT Schema Bindings Accepted in Less Than 10 Iterations
22mtsdown: One tool to bundle them all
23mJSDocs: It's like TypeScript but without all that TypeScript
47mInteractive development with Dotty
39mStatus of DTS Validation in Linux Kernel
01h 24mExtending clang-tidy in the Present and in the Future