From: Eduardo Valentin <edubezval@gmail.com>
To: Javi Merino <javi.merino@arm.com>
Cc: linux-pm@vger.kernel.org, linux-doc@vger.kernel.org,
Amit Daniel Kachhap <amit.kachhap@linaro.org>,
Jonathan Corbet <corbet@lwn.net>, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH] Documentation: thermal: document of_cpufreq_cooling_register()
Date: Tue, 6 Jan 2015 14:39:37 -0400 [thread overview]
Message-ID: <20150106183936.GB11119@developer> (raw)
In-Reply-To: <1420568065-5153-1-git-send-email-javi.merino@arm.com>
[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]
On Tue, Jan 06, 2015 at 06:14:25PM +0000, Javi Merino wrote:
> Commit 39d99cff76bf ("thermal: cpu_cooling: introduce
> of_cpufreq_cooling_register") taught the cpu cooling device to register
> devices that were linked to the device tree but didn't update the
> cpu-cooling-api documentation. Fix it.
>
> Cc: Amit Daniel Kachhap <amit.kachhap@linaro.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Zhang Rui <rui.zhang@intel.com>
> Cc: Eduardo Valentin <edubezval@gmail.com>
> Signed-off-by: Javi Merino <javi.merino@arm.com>
Thanks, applied to my -fixes branch.
> ---
> Documentation/thermal/cpu-cooling-api.txt | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/thermal/cpu-cooling-api.txt b/Documentation/thermal/cpu-cooling-api.txt
> index fca24c931ec8..753e47cc2e20 100644
> --- a/Documentation/thermal/cpu-cooling-api.txt
> +++ b/Documentation/thermal/cpu-cooling-api.txt
> @@ -3,7 +3,7 @@ CPU cooling APIs How To
>
> Written by Amit Daniel Kachhap <amit.kachhap@linaro.org>
>
> -Updated: 12 May 2012
> +Updated: 6 Jan 2015
>
> Copyright (c) 2012 Samsung Electronics Co., Ltd(http://www.samsung.com)
>
> @@ -25,7 +25,18 @@ the user. The registration APIs returns the cooling device pointer.
>
> clip_cpus: cpumask of cpus where the frequency constraints will happen.
>
> -1.1.2 void cpufreq_cooling_unregister(struct thermal_cooling_device *cdev)
> +1.1.2 struct thermal_cooling_device *of_cpufreq_cooling_register(
> + struct device_node *np, const struct cpumask *clip_cpus)
> +
> + This interface function registers the cpufreq cooling device with
> + the name "thermal-cpufreq-%x" linking it with a device tree node, in
> + order to bind it via the thermal DT code. This api can support multiple
> + instances of cpufreq cooling devices.
> +
> + np: pointer to the cooling device device tree node
> + clip_cpus: cpumask of cpus where the frequency constraints will happen.
> +
> +1.1.3 void cpufreq_cooling_unregister(struct thermal_cooling_device *cdev)
>
> This interface function unregisters the "thermal-cpufreq-%x" cooling device.
>
> --
> 1.9.1
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-01-06 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 18:14 [PATCH] Documentation: thermal: document of_cpufreq_cooling_register() Javi Merino
2015-01-06 18:39 ` Eduardo Valentin [this message]
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=20150106183936.GB11119@developer \
--to=edubezval@gmail.com \
--cc=amit.kachhap@linaro.org \
--cc=corbet@lwn.net \
--cc=javi.merino@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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).