Re: [PATCH 07/10] cpufreq: dt: Add support for some new Allwinner SoCs

On Tue, Aug 15, 2017 at 8:25 PM, Rafael J. Wysocki [off-list ref] wrote:

On Tuesday, August 15, 2017 7:42:19 AM CEST Chen-Yu Tsai wrote:

quoted

On Mon, Jul 24, 2017 at 7:46 PM, Rafael J. Wysocki [off-list ref] wrote:

quoted

On Monday, July 24, 2017 02:23:49 PM Viresh Kumar wrote:

quoted

On 23-07-17, 18:27, Icenowy Zheng wrote:

quoted

Some new Allwinner SoCs get supported in the kernel after the
compatibles are added to cpufreq-dt-platdev driver.

Add their compatible strings in the cpufreq-dt-platdev driver.

Cc: "Rafael J. Wysocki" <redacted>
Cc: Viresh Kumar <redacted>
Signed-off-by: Icenowy Zheng <redacted>
---
 drivers/cpufreq/cpufreq-dt-platdev.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
index 2eb40d46d357..c3851453e84a 100644
--- a/drivers/cpufreq/cpufreq-dt-platdev.c
+++ b/drivers/cpufreq/cpufreq-dt-platdev.c

@@ -24,7 +24,11 @@ static const struct of_device_id machines[] __initconst = {
    { .compatible = "allwinner,sun8i-a23", },
    { .compatible = "allwinner,sun8i-a33", },
    { .compatible = "allwinner,sun8i-a83t", },
+   { .compatible = "allwinner,sun8i-h2-plus", },
    { .compatible = "allwinner,sun8i-h3", },
+   { .compatible = "allwinner,sun8i-v3s", },
+   { .compatible = "allwinner,sun50i-a64", },
+   { .compatible = "allwinner,sun50i-h5", },

    { .compatible = "apm,xgene-shadowcat", },

@@ -43,6 +47,8 @@ static const struct of_device_id machines[] __initconst = {
    { .compatible = "marvell,pxa250", },
    { .compatible = "marvell,pxa270", },

+   { .compatible = "nextthing,gr8", },
+
    { .compatible = "samsung,exynos3250", },
    { .compatible = "samsung,exynos4210", },
    { .compatible = "samsung,exynos4212", },

Acked-by: Viresh Kumar <redacted>

OK

I'm assuming this will go in via arm-soc along with the rest of the series.

The rest of the series, except for the clk patches I've already taken,
doesn't seem to be going anywhere just yet. Is there a cpufreq or pm tree
this can be merged through?

You mean this particular patch or the whole series?

If the former, then yes, there is.

Just this patch. As I mentioned the rest of the series still needs some
work, and likely won't make it in this cycle. If you could take this
through the tree it would normally go through, avoiding any conflicts,
that'd be great.

ChenYu