public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"srivatsa.bhat@linux.vnet.ibm.com"
	<srivatsa.bhat@linux.vnet.ibm.com>,
	"ego@linux.vnet.ibm.com" <ego@linux.vnet.ibm.com>,
	"svaidy@linux.vnet.ibm.com" <svaidy@linux.vnet.ibm.com>
Subject: Re: [PATCH] cpufreq: create another field .flags in cpufreq_frequency_table
Date: Fri, 28 Mar 2014 11:19:43 +0100	[thread overview]
Message-ID: <20140328111943.272d0bea@amdc2363> (raw)
In-Reply-To: <b5bc276cdd34b039de2aa640ec0bb5dff195f832.1395996386.git.viresh.kumar@linaro.org>

Hi Viresh,

> diff --git a/drivers/cpufreq/exynos4x12-cpufreq.c
> b/drivers/cpufreq/exynos4x12-cpufreq.c index 7c11ace..8c4c6a5 100644
> --- a/drivers/cpufreq/exynos4x12-cpufreq.c
> +++ b/drivers/cpufreq/exynos4x12-cpufreq.c
> @@ -30,21 +30,21 @@ static unsigned int exynos4x12_volt_table[] = {
>  };
> 
>  static struct cpufreq_frequency_table exynos4x12_freq_table[] = {
> -       {CPUFREQ_BOOST_FREQ, 1500 * 1000},
> -       {L1, 1400 * 1000},
> -       {L2, 1300 * 1000},
> -       {L3, 1200 * 1000},
> -       {L4, 1100 * 1000},
> -       {L5, 1000 * 1000},
> -       {L6,  900 * 1000},
> -       {L7,  800 * 1000},
> -       {L8,  700 * 1000},
> -       {L9,  600 * 1000},
> -       {L10, 500 * 1000},
> -       {L11, 400 * 1000},
> -       {L12, 300 * 1000},
> -       {L13, 200 * 1000},
> -       {0, CPUFREQ_TABLE_END},
> +       {CPUFREQ_BOOST_FREQ, 0, 1500 * 1000},
> +       {0, L1, 1400 * 1000},
> +       {0, L2, 1300 * 1000},
> +       {0, L3, 1200 * 1000},
> +       {0, L4, 1100 * 1000},
> +       {0, L5, 1000 * 1000},
> +       {0, L6,  900 * 1000},
> +       {0, L7,  800 * 1000},
> +       {0, L8,  700 * 1000},
> +       {0, L9,  600 * 1000},
> +       {0, L10, 500 * 1000},
> +       {0, L11, 400 * 1000},
> +       {0, L12, 300 * 1000},
> +       {0, L13, 200 * 1000},
> +       {0, 0, CPUFREQ_TABLE_END},
>  };

Looks correct for me.

One little remark - since cpufreq_frequency_tables are defined as
static it seems like we don't need to explicitly specify the 0, for
flags field.

Something like {, L13, 200 * 1000}, shall be enough.

> +/* Special Values of .flags field */
> +#define CPUFREQ_BOOST_FREQ     0x1

Maybe (1 << 0) to explicitly show that those are flags.

> 
>  struct cpufreq_frequency_table {
> +       unsigned int    flags;
>         unsigned int    driver_data; /* driver specific data, not

The driver_data shall be changed to int. However I suppose that it will
be done at separate patch.

> used by core */ unsigned int    frequency; /* kHz - doesn't need to
> be in ascending
>                                     * order */

-- 
Best regards,

Lukasz Majewski

Samsung R&D Institute Poland (SRPOL) | Linux Platform Group

  parent reply	other threads:[~2014-03-28 10:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  6:48 [PATCH] cpufreq: set value of CPUFREQ_BOOST_FREQ to 0xABABABAB Viresh Kumar
2014-03-24  8:21 ` Lukasz Majewski
2014-03-24  8:33   ` Viresh Kumar
2014-03-24  8:52 ` Gautham R Shenoy
2014-03-28  8:53 ` [PATCH] cpufreq: create another field .flags in cpufreq_frequency_table Viresh Kumar
2014-03-28 10:14   ` [PATCH] cpufreq: use kzalloc() to allocate memory for cpufreq_frequency_table Viresh Kumar
2014-03-28 10:44     ` Gautham R Shenoy
2014-03-28 13:29     ` Joe Perches
2014-03-28 13:32       ` Viresh Kumar
2014-03-28 10:19   ` Lukasz Majewski [this message]
2014-03-28 10:33     ` [PATCH] cpufreq: create another field .flags in cpufreq_frequency_table Viresh Kumar
2014-03-28 10:43   ` Gautham R Shenoy
2014-03-28  8:55 ` [PATCH] cpufreq: set value of CPUFREQ_BOOST_FREQ to 0xABABABAB Viresh Kumar

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=20140328111943.272d0bea@amdc2363 \
    --to=l.majewski@samsung.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=ego@linux.vnet.ibm.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=svaidy@linux.vnet.ibm.com \
    --cc=viresh.kumar@linaro.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