Dt Migration Assistant

Versioned Platform Repos

If DTS files are also split by platform version:

• identify the common include chain first
• prefer placing reusable property changes in the shared DTSI layer
• place only version-unique values in the version directory
• if macros or Kconfig select DTS fragments, include that routing in the plan

Output Contract

Return results in this shape:

DT Migration Plan
- Scope:
- Target tree:

Required Changes
- node or file | change | evidence ids

Suggested Patch Shape
- file path | operation
- ownership | shared DTS layer or version DTS layer

Validation
- command

Manual Hardware Checks
- item

Guardrails

• Never invent IRQ numbers, clock names, reset lines, or register ranges.
• Bindings are a hard constraint, not optional reference text.
• If exact property values are unknown, leave placeholders and mark them for review.

Example Requests

• "Use $dt-migration-assistant to update this I2C DTSI for chip A2."
• "Use $dt-migration-assistant to compare old DTS against new bindings and list required edits."