Skip to content

ARM DT cpus/cpu and topology bindings

Rob Herring linux-arm-kernel linux-devicetree 2 versions – New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest posting 2/20 of 2 patches 0 repliesNew
  2. v2 posting 1/20 of 2 patches 0 repliesSuperseded

Patches in v2 posting 2/2 No applies recorded yet

None of the 2 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [PATCH v2 0/2] ARM DT cpus/cpu and topology bindings
Quoted 10 lines · Lorenzo Pieralisi
Quoted 8 lines · Rob Herring
Quoted 4 lines · Lorenzo Pieralisi

[replying to self]

Any further comments on this series ? If not, I think bindings are ready to be queued, but for that I need acks from DT maintainers.

Who do you plan to take this? Is this dependent on something for 3.13? If not, I'll apply it.

Quoted 9 lines

v3 on the lists, should be final. No, there are no dependencies on 3.13 to the best of my knowledge. The problem with pre-v7 UP systems with cpus node #address-cells == 0 is still there and I would like to ask you please what we/I should do about that, it can trigger a considerable amount of churn. As soon as these bindings hit the mainline I will update the DT parsing code, I can easily take all pre-v7 UP dts out of the picture in the parsing loop (after all, reg property for those processors is useless), but the dts are _wrong_ regardless when these patches become the official bindings.

Given that this is really a don't care for the kernel, I'm not sure what kernel change you are thinking. It is not the kernel's job to validate the dtb, so I think the kernel should not care. We should do this sort of validation at dtb build time at the latest. As to updating the dts files, yes we should probably do that.

Rob