设备树根节点model字段的作用与必要性技术问询

Great question—this is one of those device tree details that’s everywhere but not always clearly spelled out. Let’s break it down:

Is model a mandatory property? #

• Short answer: No, it’s not strictly required by the official Device Tree Specification. The spec defines it as an optional root node property, meant to provide a human-readable description of the hardware.
• That said, you’ll see it in nearly every device tree because it’s become a de facto convention, and some bootloaders or vendor-specific board support packages (BSPs) may expect it for compatibility or logging. But from the kernel’s perspective (per the spec), your system can boot and function correctly without it.

Core meaning of the model property #

This property serves two key roles:

1. Human-readable hardware identification: It’s a clear, plain-language string that tells you exactly what board/platform the device tree targets (e.g., Freescale i.MX6Lite SABRE SD Board in your imx6l-sabresd.dts). This is huge for debugging, logging, and quickly orienting yourself when working with multiple device trees—no need to parse dozens of nodes to figure out which hardware you’re dealing with.
2. Firmware/kernel compatibility hooks: While you only found Freescale’s kernel code accessing it, many bootloaders (like U-Boot) or vendor-specific kernel code use this string to run platform-specific setup. For example, U-Boot might check the model string to load the right configuration or initialize certain peripherals before handing off to the kernel. Even if mainline kernel code doesn’t rely on it universally, vendor BSPs often use it for backward compatibility with older hardware or custom workflows.

Why is it in almost every device tree, then? #

• Convention and maintainability: It’s a best practice to include model because it makes device trees self-documenting. Anyone reading the file can immediately understand its target hardware, which is critical for long-term maintenance.
• Legacy inertia: Early device tree implementations from SoC vendors (like Freescale) standardized on including model, and the practice stuck as device trees became the standard for hardware description. Since including it has no downsides, most developers keep adding it even if their platform’s kernel code doesn’t explicitly use it.

内容的提问来源于stack exchange，提问作者md.jamal