linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Jonathan Corbet <corbet@lwn.net>, Zhang Rui <rui.zhang@intel.com>,
	Eduardo Valentin <edubezval@gmail.com>,
	Javi Merino <javi.merino@arm.com>,
	Punit Agrawal <punit.agrawal@arm.com>,
	Daniel Kurtz <djkurtz@chromium.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org,
	Daniel Thompson <daniel.thompson@linaro.org>
Subject: Re: [PATCH v2 0/4] thermal: re-calculate k_po/k_pu when update sustainable power
Date: Wed, 6 Jan 2016 16:48:23 +0800	[thread overview]
Message-ID: <20160106084823.GA1641@leoy-linaro> (raw)
In-Reply-To: <1452069023-32149-1-git-send-email-leo.yan@linaro.org>

Hi all,

On Wed, Jan 06, 2016 at 04:30:19PM +0800, Leo Yan wrote:
> k_po/k_pu are two proportional term constants and essentially they have
> fixed ratio compared with sustainable power. In current implementation,
> k_po and k_pu are absolute value after calculation and cannot represent
> the ratio relationship with sustainable power; as a result, when change
> sustainable power we cannot smoothly change proportional term constant.
> 
> So this patch series introduces k_po_ratio and k_pu_ratio, which
> represent the ratio value compared against sustainable power. Also add
> sys file system nodes for them for easily update them from userspace and
> update a bit in documentation.
> 
> Changes from v1:
> * According to Eduardo' comments, move code from thermal_core to
>   power_allocator file
> * According to Daniel's review, v1 will introduce accumulated rounding
>   errors; v2 patches can dismiss this issue
> 
> Leo Yan (4):
>   thermal: power_allocator: rework proportional parameter
>   thermal: power_allocator: change k_pu_ratio/k_po_ratio as percentage
>   thermal: add sys node for k_pu_ratio/k_po_ratio
>   thermal: power_allocator: document k_pu_ratio/k_po_ratio
> 
>  Documentation/thermal/power_allocator.txt | 15 +++++++++++----
>  drivers/thermal/power_allocator.c         | 18 ++++++++++++------
>  drivers/thermal/thermal_core.c            | 23 +++++++++++++++++++++--
>  include/linux/thermal.h                   |  4 ++--
>  4 files changed, 46 insertions(+), 14 deletions(-)

Sorry for confusion.

I recognized I used duplicated version number, please drop this series;
I will send a new v3 series.

Thanks,
Leo Yan

      parent reply	other threads:[~2016-01-06  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06  8:30 [PATCH v2 0/4] thermal: re-calculate k_po/k_pu when update sustainable power Leo Yan
2016-01-06  8:30 ` [PATCH v2 1/4] thermal: power_allocator: rework proportional parameter Leo Yan
2016-01-06  8:30 ` [PATCH v2 2/4] thermal: power_allocator: change k_pu_ratio/k_po_ratio as percentage Leo Yan
2016-01-06  8:30 ` [PATCH v2 3/4] thermal: add sys node for k_pu_ratio/k_po_ratio Leo Yan
2016-01-06  8:30 ` [PATCH v2 4/4] thermal: power_allocator: document k_pu_ratio/k_po_ratio Leo Yan
2016-01-06  8:48 ` Leo Yan [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=20160106084823.GA1641@leoy-linaro \
    --to=leo.yan@linaro.org \
    --cc=corbet@lwn.net \
    --cc=daniel.thompson@linaro.org \
    --cc=djkurtz@chromium.org \
    --cc=edubezval@gmail.com \
    --cc=javi.merino@arm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=punit.agrawal@arm.com \
    --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).