How to Get Your DT Schema Bindings Accepted in Less Than 10 Iterations
summary
Claim: new DT bindings can land in under ten review iterations by following concrete rules and running the validator before submission. The talk shows using DT schema YAML, installing the Python dt-schema package and running make check_dtb or the dt-validate tool to catch mismatches between binding and DTS, favors strict arrays and vendor-prefixed properties, and recommends finishing bindings with additionalProperties: false (or unevaluatedProperties when referencing common schemas). Real-world outcome: fewer DTC warnings and faster, smaller review cycles.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:48Bindings and Devicetree schema
- 6:49Generic rules for bindings-compatibles
- 8:42Generic rules for bindings-syscon and simple-mfd
- 11:06Generic rules for bindings-properties
- 20:55Dos and Don'ts-additional/unevaluated
related talks
22mDT formatter - a maintainer's and contributor's elusive dream?
21mHow TDD and CDD make your apps suck less
01h 29mTest-Driven Data Analysis
22mStop Reviewing Schemas: How Intuit Made Developers Faster by Automating Governance
30mAccelerating the Dev Loop with DCM Lints at Betterment
32mTDD – Trust Driven Development
47mDevelopment Best Practices: An Overview of Working in the Software World
32mLooks GREAT To Me: Getting Past Bare Minimum Code Reviews