Skip to content

RFC ARM: mv78x00: First step to convert mv78x00 to Device Tree

Andrew Lunn linux-arm-kernel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest1 of 5 patches 0 repliesNew

1 of 5 patches is in this archive. The cover letter announces 5.

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
2/5ARM: mv78x00: Convert RD-78X00-mASA board to device tree+0 -02 replies

Reviews trailers per patch

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

Read the v1 thread

Cover letter [RFC PATCH 0/5] ARM: mv78x00: First step to convert mv78x00 to Device Tree
Quoted 30 lines · Gregory CLEMENT
Quoted 18 lines · Andrew Lunn
Quoted 17 lines · Gregory CLEMENT

Hello,

This patch set is a first step in order to convert mach-mv78x00 to device tree before it joins mach-mvebu.

I managed to test it on the RD-78X00-mASA board. All the peripherals I have tested work as they work before the migration to the device tree:
- UART
- Ethernet
- USB
- SATA

My main concern is that the mv78x00 are MP but not SMP capable. Currently the same kernel run on the 2 cores and it is in the board file that the peripherals are assigned for each CPU. (Actually I didn't test this behavior, but the code is written in this way.)

Quoted 7 lines
Quoted 5 lines

I don't know how to assign a peripheral to a given CPU with the device tree. The only way I have in mind is to have a dts per CPU, but I am not sure it is very convenient.

So for now the code assigns all the peripherals to the CPU.

Hi Gregory

Hi Andrew,

Quoted 1 line
Quoted 7 lines
Quoted 3 lines

Could you explain what you have in a bit more detail. Are you just bringing up one CPU and assigning all peripherals to that? Or do all peripherals get assigned to the first CPU but both are running?

Currently I didn't find (but I didn't looked for so much) how to boot the kernel on both CPU even with the legacy code. So I am just bringing up one CPU and assigning all peripherals to that.

Hi Gregory

Did you try looking at UART 1. It could be there is a second uboot instance running on it which is for CPU1.

Quoted 4 lines
Quoted 2 lines

It might be interesting to ask on the buffalo forums if anybody is actually using mainline on TS-WLX.

Do you know where is this forum?

http://forum.buffalo.nas-central.org

Andrew