public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: use the cpufreq-dt platform_data for independent clocks
Date: Tue, 2 Dec 2014 12:03:24 -0500	[thread overview]
Message-ID: <20141202170324.GY22670@titan.lakedaemon.net> (raw)
In-Reply-To: <1417538882-19254-1-git-send-email-thomas.petazzoni@free-electrons.com>

Arnd, ThomasP,

On Tue, Dec 02, 2014 at 05:48:02PM +0100, Thomas Petazzoni wrote:
> This commit adjusts the registration of the cpufreq-dt driver in the
> mvebu platform to indicate to the cpufreq driver that the platform has
> independent clocks for each CPU.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> Jason, this commit was part of my "[PATCHv2 0/4] cpufreq-dt,
> platform_data based proposal" series, which included 3 patches for
> drivers/cpufreq/, and this last patch for mach-mvebu to make use of
> the new cpufreq feature. However, in order to not confuse the cpufreq
> maintainer, when I sent "[PATCH v3 0/3] cpufreq: cpufreq-dt:
> platform_data based proposal", I didn't include this patch for
> mach-mvebu.
> 
> But now, it means that this is the only missing piece to get cpufreq
> working on Armada XP. Do you think you could squeeze it into the
> things merged for 3.19 ? It's a very small patch, so hopefully it's
> still possible to do so.

I have no problem with it except logistical.  :(  I'm currently on
travel and my well-tested, but hacked up connection to my development
box went down.  I've no way to apply this until this weekend at best.

Acked-by; Jason Cooper <jason@lakedaemon.net>

Arnd, would you mind taking this directly onto mvebu/soc?  I've nothing
else in the queue (just the one pending pull request for soc-suspend)

Or, would it be acceptable for this to be /fixes-non-critical for -rc1?


thx,

Jason.

> The patch is based on mvebu/soc.
> ---
>  arch/arm/mach-mvebu/pmsu.c | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/mach-mvebu/pmsu.c b/arch/arm/mach-mvebu/pmsu.c
> index 5a757f9..d8ab605 100644
> --- a/arch/arm/mach-mvebu/pmsu.c
> +++ b/arch/arm/mach-mvebu/pmsu.c
> @@ -20,6 +20,7 @@
>  
>  #include <linux/clk.h>
>  #include <linux/cpu_pm.h>
> +#include <linux/cpufreq-dt.h>
>  #include <linux/delay.h>
>  #include <linux/init.h>
>  #include <linux/io.h>
> @@ -571,6 +572,10 @@ int mvebu_pmsu_dfs_request(int cpu)
>  	return 0;
>  }
>  
> +struct cpufreq_dt_platform_data cpufreq_dt_pd = {
> +	.independent_clocks = true,
> +};
> +
>  static int __init armada_xp_pmsu_cpufreq_init(void)
>  {
>  	struct device_node *np;
> @@ -643,7 +648,8 @@ static int __init armada_xp_pmsu_cpufreq_init(void)
>  		}
>  	}
>  
> -	platform_device_register_simple("cpufreq-dt", -1, NULL, 0);
> +	platform_device_register_data(NULL, "cpufreq-dt", -1,
> +				      &cpufreq_dt_pd, sizeof(cpufreq_dt_pd));
>  	return 0;
>  }
>  
> -- 
> 2.1.0
> 

  reply	other threads:[~2014-12-02 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 16:48 [PATCH] ARM: mvebu: use the cpufreq-dt platform_data for independent clocks Thomas Petazzoni
2014-12-02 17:03 ` Jason Cooper [this message]
2014-12-04 16:32   ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141202170324.GY22670@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox