ARM: shmobile: r8a7740/armadillo800eva legacy PM domain support
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest posting 2/20 of 11 patches 0 repliesNew
- v2 posting 1/20 of 11 patches 0 repliesSuperseded
- v10 of 11 patches 0 repliesSuperseded
Patches in v2 posting 2/2 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 v2 yet.
Cover letter [PATCH v2 00/11] ARM: shmobile: r8a7740/armadillo800eva legacy PM domain support
Quoted 26 lines · Geert Uytterhoeven
Hi Magnus,
Quoted 8 lines · Magnus Damm
Quoted 8 lines
Quoted 1 line
So what is a good way to proceed with this series I wonder?
There are two options:
1. Drop the two patches that introduce the D4 and A4MP PM domains,
2. Amend the patches that introduce the D4 and A4MP PM domains to comment out the entries in the table inpm-r8a7740.c, like was done in the first submission.Quoted 7 lines
Quoted 4 lines
Both will cause conflicts when applying the successive patches.
If you don't care about bisectability, you can implement option 2 as a separate change, after applying the whole series.
Thanks for leading the way! From my side I don't have any special feeling, so why don't you and Simon decide?
OK.
Quoted 4 lines
If it was up to me only then I think option #1 that simply reduces the feature set seems rather natural, but perhaps it requires a lot of rework of the patches. If we go with option #1 we can always incrementally add D4 and A4MP later I assume.
Quoted 5 lines
Yes we can.
Please wait a bit, I'm looking into the !CONFIG_PM_RUNTIME case. Mostly multi-platform, but it may affect legacy too, where there's interaction with the
drivers/sh/pm_runtime.chack.
I also feel that option 1 is slightly nicer. But I'm happy to consider option 2 if its a better fit for you.
As always I'm happy to wait and will now do so.