ARM: shmobile: r8a7790 APMU SMP support
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest posting 4/40 of 3 patches 0 repliesNew
- v2 posting 3/40 of 3 patches 0 repliesSuperseded
- v2 posting 2/40 of 3 patches 0 repliesSuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v2 posting 1/4 | 0 of 3 patches | 0 replies | Superseded |
Patches in v2 posting 4/4 No applies recorded yet
None of the 3 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.
Cover letter [PATCH v2 00/03] ARM: shmobile: r8a7790 APMU SMP support
Quoted 45 lines · Sudeep KarkadaNagesha
Quoted 32 lines · Simon Horman
Quoted 31 lines · Simon Horman
Quoted 20 lines · Magnus Damm
Quoted 19 lines · Simon Horman
Quoted 18 lines · Magnus Damm
ARM: shmobile: r8a7790 APMU SMP support
[PATCH v2 01/03] ARM: shmobile: Shared APMU SMP support code without DT [PATCH v2 02/03] ARM: shmobile: Add r8a7790 SMP support using APMU code [PATCH v2 03/03] ARM: shmobile: Add r8a7790 CA15 CPU cores
This series adds SMP support to r8a7790 using the included APMU code. The previous version of r8a7790 support depended on the APMU code in "[PATCH] ARM: shmobile: Shared APMU SMP support code", but in this version the APMU code has been reworked to not use DT. In the future r8a73a4 and other SoCs may make use of the APMU as well, but the r8a73a4 code first needs to be adjusted to work with the CCI driver.
With these patches applied r8a7790 CA15 support for SMP boot and CPU Hotplug is known to be working.
Thanks to Sudeep for his feedback.
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Signed-off-by Magnus Damm <[email protected]>Hi Magnus,
can I clarify that these patches are targeted at mainline?
Hi Simon, yes, that's correct. It's possible to back port too if needed.
Thanks for the clarification.
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
Actual merge is not rushing though, so please don't interpret this as any last minute v3.12 merge attempt.
No problem, I didn't interpret it that way.
I have queued these up for v3.13 and they are present in the freshly baked renesas-devel-20130904 tag.
As I already mentioned I asked not to add any custom bindings to support multiple cluster. But this version removed APMU node from DT completely which is not correct.
Quoted 5 lines
Also you removed multi cluster support to avoid CCI and MCPM reuse. I think you may have to rework these completely when adding multi-cluster support. I strongly recommend to reuse the CCI and MPCM code from first instead of reworking again, but I leave it SH platform maintainer to decide.
Thanks for your feedback,
I plan to meet with Magnus in person on Friday and I will discuss this issue with him in our capacities as shmobile co-maintainers.