Skip to content

ep93xx: Move SoC private bits to core

Arnd Bergmann linux-arm-kernel 3 versions – New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v4 Latest posting 3/30 of 11 patches 0 repliesNew
  2. v4 posting 2/30 of 11 patches 0 repliesSuperseded
  3. v4 posting 1/33 of 11 patches 0 repliesSuperseded

Patches in v4 posting 3/3 No applies recorded yet

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

Reviews trailers per patch

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

Read the v4 thread

Cover letter [PATCH v4 00/11] ep93xx: Move SoC private bits to core
Quoted 16 lines · H Hartley Sweeten
Quoted 5 lines · Arnd Bergmann

As the first steps (after reading Documentation/devicetree/booting-without-of.txt) the best way forward is probably to take you favourite board file and add a DT_MACHINE_START section so you can boot the same machine
when passing an empty devicetree rather than ATAGS. Then add the interrupt controller (should be simple for VIC), followed by gpio (needs bindings,

Quoted 8 lines

see Documentation/devicetree/bindings/gpio/*.txt), i2c and spi. After you have all that infrastructure in place, you can convert every other device, one at a time. Some (anything without platform_data) will be Trivial, others require you to come up with a new binding document and properties to replace the platform_data. Many people try to do the ones from board files first because it lets them remove the board files, and only after that look at converting the core devices, but you can do any order you like.

Quoted 2 lines

The main problem I see with converting the ep93xx platform to device tree is that it requires modifying the bootloader. Correct me if I am wrong.

You can always use legacy bootloaders with an appended device tree. It's slightly less interesting that way but it still works. You can also use a second-stage boot loader, but that would require having one that supports your platform.

Arnd