All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: rjw@rjwysocki.net, sboyd@codeaurora.org, shawn.guo@linaro.org
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, arvind.chauhan@arm.com,
	mturquette@linaro.org, linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, spk.linux@gmail.com,
	thomas.ab@samsung.com, nm@ti.com, t.figa@samsung.com,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 1/2] cpufreq: Add support for per-policy driver data
Date: Wed, 25 Jun 2014 14:12:28 +0530	[thread overview]
Message-ID: <28dc4ae67a7c3c712714abc14619b7c1d4bfb361.1403684824.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1403684824.git.viresh.kumar@linaro.org>
In-Reply-To: <cover.1403684824.git.viresh.kumar@linaro.org>

Drivers supporting multiple clusters or multiple 'struct cpufreq_policy'
instances may need to keep some per-policy data. If the core doesn't support
them, they might do it in the most unoptimized way: per-cpu data.

This patch adds another field in 'struct cpufreq_policy': driver_data. It isn't
accessed by core and is completely for driver's internal use.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
 include/linux/cpufreq.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
index ec4112d..d4b1108 100644
--- a/include/linux/cpufreq.h
+++ b/include/linux/cpufreq.h
@@ -112,6 +112,9 @@ struct cpufreq_policy {
 	spinlock_t		transition_lock;
 	wait_queue_head_t	transition_wait;
 	struct task_struct	*transition_task; /* Task which is doing the transition */
+
+	/* For cpufreq driver's internal use */
+	void			*driver_data;
 };
 
 /* Only for ACPI */
-- 
2.0.0.rc2

WARNING: multiple messages have this Message-ID
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] cpufreq: Add support for per-policy driver data
Date: Wed, 25 Jun 2014 14:12:28 +0530	[thread overview]
Message-ID: <28dc4ae67a7c3c712714abc14619b7c1d4bfb361.1403684824.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1403684824.git.viresh.kumar@linaro.org>

Drivers supporting multiple clusters or multiple 'struct cpufreq_policy'
instances may need to keep some per-policy data. If the core doesn't support
them, they might do it in the most unoptimized way: per-cpu data.

This patch adds another field in 'struct cpufreq_policy': driver_data. It isn't
accessed by core and is completely for driver's internal use.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
 include/linux/cpufreq.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
index ec4112d..d4b1108 100644
--- a/include/linux/cpufreq.h
+++ b/include/linux/cpufreq.h
@@ -112,6 +112,9 @@ struct cpufreq_policy {
 	spinlock_t		transition_lock;
 	wait_queue_head_t	transition_wait;
 	struct task_struct	*transition_task; /* Task which is doing the transition */
+
+	/* For cpufreq driver's internal use */
+	void			*driver_data;
 };
 
 /* Only for ACPI */
-- 
2.0.0.rc2

  reply	other threads:[~2014-06-25  8:43 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  8:42 [PATCH 0/2] cpufreq: cpu0: Extend support beyond CPU0 Viresh Kumar
2014-06-25  8:42 ` Viresh Kumar
2014-06-25  8:42 ` Viresh Kumar [this message]
2014-06-25  8:42   ` [PATCH 1/2] cpufreq: Add support for per-policy driver data Viresh Kumar
2014-06-25  8:42 ` [PATCH 2/2] cpufreq: cpu0: Extend support beyond CPU0 Viresh Kumar
2014-06-25  8:42   ` Viresh Kumar
2014-06-25 19:02   ` Stephen Boyd
2014-06-25 19:02     ` Stephen Boyd
2014-06-26  1:55     ` Viresh Kumar
2014-06-26  1:55       ` Viresh Kumar
2014-06-26  1:55       ` Viresh Kumar
2014-06-26  7:34     ` Viresh Kumar
2014-06-26  7:34       ` Viresh Kumar
2014-06-26  7:34       ` Viresh Kumar
2014-06-26 10:52     ` Viresh Kumar
2014-06-26 10:52       ` Viresh Kumar
2014-06-26 10:52       ` Viresh Kumar
2014-06-27  0:06       ` Stephen Boyd
2014-06-27  0:06         ` Stephen Boyd
2014-06-27  0:06         ` Stephen Boyd
2014-06-27  1:53         ` Mike Turquette
2014-06-27  1:53           ` Mike Turquette
2014-06-27  1:53           ` Mike Turquette
2014-06-27  2:15           ` Viresh Kumar
2014-06-27  2:15             ` Viresh Kumar
2014-06-27  2:15             ` Viresh Kumar
2014-06-30  7:57             ` Viresh Kumar
2014-06-30  7:57               ` Viresh Kumar
2014-06-30  7:57               ` Viresh Kumar
2014-06-30 18:33               ` Rob Herring
2014-06-30 18:33                 ` Rob Herring
2014-06-30 18:33                 ` Rob Herring
2014-07-01 11:14                 ` Viresh Kumar
2014-07-01 11:14                   ` Viresh Kumar
2014-07-01 11:14                   ` Viresh Kumar
2014-07-01 22:00                   ` Mike Turquette
2014-07-01 22:00                     ` Mike Turquette
2014-07-01 22:00                     ` Mike Turquette
2014-07-02  3:32                     ` Viresh Kumar
2014-07-02  3:32                       ` Viresh Kumar
2014-07-02  3:32                       ` Viresh Kumar
2014-06-27  2:26         ` Viresh Kumar
2014-06-27  2:26           ` Viresh Kumar
2014-06-27  2:26           ` Viresh Kumar
2014-06-26 22:08     ` Mark Brown
2014-06-26 22:08       ` Mark Brown
2014-06-28 14:52   ` Shawn Guo
2014-06-28 14:52     ` Shawn Guo
2014-06-28 14:52     ` Shawn Guo
2014-06-30  4:50     ` Viresh Kumar
2014-06-30  4:50       ` Viresh Kumar
2014-06-30  4:50       ` 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=28dc4ae67a7c3c712714abc14619b7c1d4bfb361.1403684824.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=arvind.chauhan@arm.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=nm@ti.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@codeaurora.org \
    --cc=shawn.guo@linaro.org \
    --cc=spk.linux@gmail.com \
    --cc=t.figa@samsung.com \
    --cc=thomas.ab@samsung.com \
    --subject='Re: [PATCH 1/2] cpufreq: Add support for per-policy driver data' \
    /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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.