Re: Devicetree spec: Specifying /cpus/cpu@* unit address format?
Rob Herring <[email protected]> Mon, 6 Apr 2026 07:48:51 -0500
| Newsgroups | org.kernel.vger.devicetree-spec,dev.linux.lists.sophgo,org.infradead.lists.linux-riscv,org.kernel.vger.linux-devicetree |
|---|---|
| Message-ID | <CAL_JsqJFv3+UJ-bjLGk0i7Wc+spsowCrqQZ_s3P4gN8r1W-Q-w@mail.gmail.com> |
On Sat, Apr 4, 2026 at 11:43=E2=80=AFPM David Gibson <[email protected]> wrote: > > On Fri, Apr 03, 2026 at 06:06:17PM +0800, Vivian Wang wrote: > > (Also posted at: https://github.com/devicetree-org/devicetree-specifica= tion/issues/86 ) > > > > Hi all, > > > > Presently, there seems to be some confusion in the community about the > > format of unit addresses for "/cpus/cpu@*" nodes for a CPU with ID > 9,= e.g. > > > > cpu@??? { > > reg =3D <10>; > > /* reg =3D <0xa>; */ /* This should be equivalent */ > > } > > > > > > Should this be a decimal "cpu@10", or hexadecimal "cpu@a"? I can't find > > any explicit specification. > > It should be hex. That's a general convention for unit addresses. > Before flattened trees, OF essentially never used decimal > representations of things. The only decimal usage in FDT were mistakes. Rather than worrying about what the spec says, please worry about what the tools check. Unfortunately, this is still only checked for specific bus types and the default is not checked. Rob