linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-pm@lists.linux-foundation.org
Cc: linux-samsung-soc@vger.kernel.org,
	Kyungmin Park <kmpark@infradead.org>,
	SangWook Ju <sw.ju@samsung.com>,
	linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org,
	linux-acpi@vger.kernel.org, Jean Delvare <khali@linux-fr.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Guenter Roeck <guenter.roeck@ericsson.com>
Subject: Re: [linux-pm] [PATCH RESEND] thermal: add generic cpufreq cooling implementation
Date: Mon, 10 Sep 2012 22:26:45 +0200	[thread overview]
Message-ID: <201209102226.45739.rjw@sisk.pl> (raw)
In-Reply-To: <201209102223.53094.rjw@sisk.pl>

On Monday, September 10, 2012, Rafael J. Wysocki wrote:
> On Monday, September 10, 2012, Zhang Rui wrote:
> > Refreshed to remove the notifier mechanism as we do not have a real user of it.
> > if there is no problem, I'll apply the whole patch set to thermal next tree.
> > 
> > From: Amit Daniel Kachhap <amit.kachhap@linaro.org>
> > Date: Thu, 16 Aug 2012 17:11:40 +0530
> > 
> > This patchset introduces a new generic cooling device based on cpufreq
> > that can be used on non-ACPI platforms.  As a proof of concept, we have
> > drivers for the following platforms using this mechanism now:
> > 
> >  * Samsung Exynos (Exynos4 and Exynos5) in the current patchset.
> >  * Freescale i.MX (git://git.linaro.org/people/amitdanielk/linux.git imx6q_thermal)
> > 
> > There is a small change in cpufreq cooling registration APIs, so a minor
> > change is needed for Freescale platforms.
> > 
> > Brief Description:
> > 
> > 1) The generic cooling devices code is placed inside driver/thermal/*
> >    as placing inside acpi folder will need un-necessary enabling of acpi
> >    code.  This code is architecture independent.
> > 
> > 2) This patchset adds generic cpu cooling low level implementation
> >    through frequency clipping.  In future, other cpu related cooling
> >    devices may be added here.  An ACPI version of this already exists
> >    (drivers/acpi/processor_thermal.c) .But this will be useful for
> >    platforms like ARM using the generic thermal interface along with the
> >    generic cpu cooling devices.  The cooling device registration API's
> >    return cooling device pointers which can be easily binded with the
> >    thermal zone trip points.  The important APIs exposed are,
> > 
> >    a) struct thermal_cooling_device *cpufreq_cooling_register(
> >         struct cpumask *clip_cpus)
> >    b) void cpufreq_cooling_unregister(struct thermal_cooling_device *cdev)
> > 
> > 3) Samsung exynos platform thermal implementation is done using the
> >    generic cpu cooling APIs and the new trip type.  The temperature sensor
> >    driver present in the hwmon folder(registered as hwmon driver) is moved
> >    to thermal folder and registered as a thermal driver.
> > 
> > A simple data/control flow diagrams is shown below,
> > 
> > Core Linux thermal <----->  Exynos thermal interface <----- Temperature Sensor
> >           |                             |
> >          \|/                            |
> >   Cpufreq cooling device <---------------
> > 
> > TODO:
> > *Will send the DT enablement patches later after the driver is merged.
> > 
> > This patch:
> > 
> > Add support for generic cpu thermal cooling low level implementations
> > using frequency scaling up/down based on the registration parameters.
> > Different cpu related cooling devices can be registered by the user and
> > the binding of these cooling devices to the corresponding trip points can
> > be easily done as the registration APIs return the cooling device pointer.
> > The user of these APIs are responsible for passing clipping frequency .
> > The drivers can also register to recieve notification about any cooling
> > action called.
> > 
> > Cc: Guenter Roeck <guenter.roeck@ericsson.com>
> > Cc: SangWook Ju <sw.ju@samsung.com>
> > Cc: Durgadoss <durgadoss.r@intel.com>
> > Cc: Len Brown <lenb@kernel.org>
> > Cc: Jean Delvare <khali@linux-fr.org>
> > Cc: Kyungmin Park <kmpark@infradead.org>
> > Cc: Kukjin Kim <kgene.kim@samsung.com>
> > Signed-off-by: Zhang Rui <rui.zhang@intel.com>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > Signed-off-by: Amit Daniel Kachhap <amit.daniel@samsung.com>
> 
> Can you please resend the patch inline (i.e. not as an attachment)?

Sorry, it was inline (obviously).  I seem to be too tired.

Please resend it to linux-pm@vger.kernel.org.  The linux-pm list at
linux-foundation.org is not functional any more.

Thanks,
Rafael

  reply	other threads:[~2012-09-10 20:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10  6:25 [PATCH RESEND] thermal: add generic cpufreq cooling implementation Zhang Rui
2012-09-10  6:50 ` Valentin, Eduardo
2012-09-10  7:20   ` Zhang Rui
2012-09-10 20:23 ` Rafael J. Wysocki
2012-09-10 20:26   ` Rafael J. Wysocki [this message]
2012-09-11  9:04 ` [linux-pm] " amit kachhap

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=201209102226.45739.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=guenter.roeck@ericsson.com \
    --cc=khali@linux-fr.org \
    --cc=kmpark@infradead.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=sw.ju@samsung.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).