Optimizing dependency tracking through DTC changes
summary
fw_devlink currently parses ~20 DT properties to find phandles, which scales poorly and misses many vendor-specific properties. Proposed fixes: have DTC emit a _references_property listing phandles, add a plugin directive to produce local fixups with phandle offsets, or change libfdt/DTC to encode per-property type metadata. Tradeoffs: size and sync-up of runtime patches, backward compatibility, and need for a DT format bump; a Rob prototype exists but no full implementation yet.
AI-written summary · about
chapters (7)
- 0:00Introduction to firmware devlink
- 2:27Current dependency tracking issues
- 3:49Proposed solutions for scaling
- 10:09Devlinks as functional requirement
- 13:19Discussion on completeness and trust
- 17:15Future DTS format and async probing
- 19:43Q&A and wrap-up
related talks
01h 10mBoF: Devicetree
44mSolving Devicetree Issues, part 3.0
44mBoF: Devicetree
50mRethinking U-Boot Devicetree Story
39mStatus of DTS Validation in Linux Kernel
34mDTS 101: From Roots To Trees, Aka Devicetree for Beginners
01h 13mDevice Tree for Dummies!
45mWhack-a-Mole with DTS Validation in the Linux Kernel