Skip to content

ARM: socfpga: Soft reset, hotplug and device tree clocks

Rob Herring linux-arm-kernel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 2 patches 0 repliesNew

Patches in v1 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 v1 yet.

Read the v1 thread

Cover letter [PATCHv1 0/2] ARM: socfpga: Soft reset, hotplug and device tree clocks
Quoted 12 lines · Pavel Machek

Hi!

Quoted 10 lines
Quoted 9 lines

From: Dinh Nguyen <[email protected]>

Hi Arnd/Olof,

Just 2 patches for mach-socfpga:

0001: ARM: socfpga: Enable hotplug and soft reset
- Able to hotplug CPU1 by putting it into reset and bringing back online.

Quoted 6 lines
Quoted 4 lines

Have you seen the discussion on PSCI? There's an ARM doc on it and Linaro session from last week. Is there a possibility you can use that? You would need to be able to run in non-secure mode and implement smc calls.

What would be the advantage?

It gets rid of some platform code. If you do an A15 part, it abstracts out the differences between the cores on entering/exiting coherency. It should also save you from writing suspend/resume and cpuidle support for your platform.

Once you do go to an A15, you will have to run in non-secure world. Once you run in non-secure mode, you cannot do everything within the kernel. So either you create custom smc calls or you use PSCI. If you really support secure mode too, then the SOC design should prevent non-secure accesses to anything that would affect the secure world like powergating a core or cache.

Quoted 2 lines

We do not have suitable hypervisor at the moment. Nor I see why it would be good to push power management into it.

It's not a hypervisor. A minimal implementation is only about 100 lines of assembly.

Quoted 1 line

(Plus, the implementation seems pretty incomplete for arm32.).

That's the point. The linux side is simple. The secure monitor side is also simplified somewhat. When you enter secure monitor mode, you are automatically running with the cache and mmu off. This avoids the side effects of cache allocations while trying to flush the caches.

Rob

Quoted 3 lines

Pavel