soc: renesas: Add R-Car SYSC PM Domain Support

Quoted 10 lines · Laurent Pinchart

Quoted 9 lines · On Friday 22 Apr 2016 10:33:11 Simon Horman wrote:

Quoted 8 lines · Geert Uytterhoeven

Quoted 7 lines · Simon Horman

Quoted 6 lines · Geert Uytterhoeven

This patch series introduces a DT-based driver for the R-Car System Controller, as found on Renesas R-Car H1, R-Car Gen2, and R-Car Gen3 SoCs.

This is a dependency for the enablement of DU and VSP on R-Car H3, as the VSPs are located in a PM Domain.

[...]

Quoted 7 lines

Quoted 4 lines

I do wonder, as we are almost at the closing point for queuing up changes for v4.7 if, assuming the above patches are scheduled for inclusion in v4.7-rc1, it might not be better for me to queue up this series for v4.8.

Then that would delay a bunch of multimedia patch by one more kernel cycle, which I was hoping to avoid.

Quoted 10 lines · Geert Uytterhoeven

Quoted 9 lines · Simon Horman

Quoted 8 lines · Geert Uytterhoeven

Quoted 7 lines · Simon Horman

Quoted 6 lines · Geert Uytterhoeven

This patch series introduces a DT-based driver for the R-Car System Controller, as found on Renesas R-Car H1, R-Car Gen2, and R-Car Gen3 SoCs.

This is a dependency for the enablement of DU and VSP on R-Car H3, as the VSPs are located in a PM Domain.

[...]

Quoted 31 lines

Quoted 3 lines

To my mind I need some kind of assurance from the clk maintainers that the patches are stable there - in particular that the commit ids won't change.

As the clock maintainer pulled the same tag instead of applying emailed patches, the commit IDs won't change, even if he has to rework the clk-next branch and repull.

Quoted 2 lines

And that both they and the ARM-SoC maintainers are happy with me pulling it into my tree for this purpose.

I also mentioned that in the pull request. Pulling in a stable branch is standard procedure: the code fails to compile if you don't merge tags/clk-renesas-for-v4.7-tag2 first.

Quoted 7 lines

I do wonder, as we are almost at the closing point for queuing up changes for v4.7 if, assuming the above patches are scheduled for inclusion in v4.7-rc1, it might not be better for me to queue up this series for v4.8.

I could do that sooner rather than later in the devel branch of the renesas tree if you like.

v4.7-rc1 is still more than one month in the future.

As Laurent said, that would delay multimedia work by one more kernel cycle, as R-Car SYSC PM Domains already missed v4.6.
In addition, it would mean continued rebasing/updating of "[PATCH v5 00/12] ARM/arm64: dts: rcar: Add SYSC PM domains" in renesas-drivers, as it touches all R-Car DTSes all over the place.

Quoted 1 line

Thanks for reconsidering!

Thanks for your feedback. I now have a better understanding of the situation both in regards to the state of the branch and the dependencies on it.

I have reconsidered and queued up this series for v4.7. It is now present in the next branch of the renesas tree.