linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: john.tobias.ph@gmail.com (John Tobias)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] ARM: imx: Add cpu frequency scaling support
Date: Wed, 18 Dec 2013 22:36:45 -0800	[thread overview]
Message-ID: <CACUGKYMQsb-eaDa1oXt38hsKzWVV=5xbNi-5-v0r8cWAMu_Rrg@mail.gmail.com> (raw)
In-Reply-To: <20131219054758.GU6691@S2101-09.ap.freescale.net>

Thanks for checking again. I should carefully check the unnecessary
braces and exercise the tools available in script.
Will re-submit again tomorrow.

Regards,

john

On Wed, Dec 18, 2013 at 9:48 PM, Shawn Guo <shawn.guo@linaro.org> wrote:
> On Wed, Dec 18, 2013 at 03:50:54PM -0800, John Tobias wrote:
>> Re-using iMX6Q driver for cpu frequency scaling.
>>
>> Signed-off-by: John Tobias <john.tobias.ph@gmail.com>
>> ---
>>  arch/arm/mach-imx/mach-imx6sl.c | 13 ++++++++++++-
>>  1 file changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/mach-imx/mach-imx6sl.c b/arch/arm/mach-imx/mach-imx6sl.c
>> index 2f952e3..a8b1543 100644
>> --- a/arch/arm/mach-imx/mach-imx6sl.c
>> +++ b/arch/arm/mach-imx/mach-imx6sl.c
>> @@ -8,7 +8,6 @@
>>   */
>>
>>  #include <linux/irqchip.h>
>> -#include <linux/of.h>
>
> This is an unrelated change to the patch.
>
>>  #include <linux/of_platform.h>
>>  #include <linux/mfd/syscon.h>
>>  #include <linux/mfd/syscon/imx6q-iomuxc-gpr.h>
>> @@ -34,6 +33,17 @@ static void __init imx6sl_fec_init(void)
>>       }
>>  }
>>
>> +static struct platform_device imx6q_cpufreq_pdev = {
>> +     .name = "imx6q-cpufreq",
>> +};
>> +
>> +static void __init imx6sl_init_late(void)
>> +{
>> +     if (IS_ENABLED(CONFIG_ARM_IMX6Q_CPUFREQ)) {
>
> Unnecessary braces.
>
>> +             platform_device_register(&imx6q_cpufreq_pdev);
>
> Register the device in the following way will save imx6q_cpufreq_pdev.
>
>         platform_device_register_simple("imx6q-cpufreq", -1, NULL, 0);
>
> Shawn
>
>> +     }
>> +}
>> +
>>  static void __init imx6sl_init_machine(void)
>>  {
>>       struct device *parent;
>> @@ -70,6 +80,7 @@ DT_MACHINE_START(IMX6SL, "Freescale i.MX6 SoloLite (Device Tree)")
>>       .map_io         = debug_ll_io_init,
>>       .init_irq       = imx6sl_init_irq,
>>       .init_machine   = imx6sl_init_machine,
>> +     .init_late      = imx6sl_init_late,
>>       .dt_compat      = imx6sl_dt_compat,
>>       .restart        = mxc_restart,
>>  MACHINE_END
>> --
>> 1.8.3.2
>>
>

  reply	other threads:[~2013-12-19  6:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 23:50 [PATCH 1/4] ARM: dts: imx6sl: Adding cpu frequency table John Tobias
2013-12-18 23:50 ` [PATCH 2/4] ARM: imx: Add cpu frequency scaling support John Tobias
2013-12-19  5:48   ` Shawn Guo
2013-12-19  6:36     ` John Tobias [this message]
2013-12-18 23:50 ` [PATCH 3/4] cpufreq: imx6q: add of_init_opp_table John Tobias
2013-12-18 23:50 ` [PATCH 4/4] PM / OPP: export symbol find_device_opp John Tobias
2013-12-19  5:54   ` Shawn Guo
2013-12-19  6:47     ` John Tobias
2013-12-19  5:42 ` [PATCH 1/4] ARM: dts: imx6sl: Adding cpu frequency table Shawn Guo
2013-12-19  6:54   ` John Tobias

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='CACUGKYMQsb-eaDa1oXt38hsKzWVV=5xbNi-5-v0r8cWAMu_Rrg@mail.gmail.com' \
    --to=john.tobias.ph@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).