Devicetree Hardware Autoconfiguration
summary
Claims that a single device tree per Allwinner SoC family can cover many cheap 7" tablets using an in-kernel hardware autodetection module that creates and applies device tree changesets. It probes I2C (touch controllers, accelerometers like the GSL1680), selects firmware blobs and pin muxing variants, and uses heuristics from unrelated parts (Wi‑Fi/accelerometer) to choose settings. Tested across ~16 personal tablets and ~60 model variants and runs upstream Linux without per‑boot overrides.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:10Tablets
- 7:16Accelerometer
- 8:46Hardware Manager
- 9:46Chinese Tablets
- 13:31Code
- 15:40Conclusion
- 17:09Devicetree Binding
- 21:51Bootloader vs Kernel
- 26:54Combination Explosion
- 29:44Boot Loader
- 32:08Devicetree
- 48:25PostBootloader
related talks
40mSecond Source Component Probing on Device Tree Platforms
01h 13mDevice Tree for Dummies!
51mShipping Multiple Devicetrees: How to Identify Which DTB Is for My Board?
50mRethinking U-Boot Devicetree Story- 40mSecond Source Component Probing on Device Tree Platforms
53mDevicetree: The Disaster so Far
01h 10mBoF: Devicetree
34mDTS 101: From Roots To Trees, Aka Devicetree for Beginners