public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Javi Merino <javi.merino@kernel.org>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: linux-pm@vger.kernel.org, edubezval@gmail.com,
	rui.zhang@intel.com, orjan.eide@arm.com, chris.diamand@arm.com
Subject: Re: [PATCH v2 0/3] devfreq_cooling: let the driver supply the real power every time we need it
Date: Tue, 21 Feb 2017 13:35:59 +0000	[thread overview]
Message-ID: <20170221133559.GC23954@ct-lt-587> (raw)
In-Reply-To: <20170131161147.17002-1-lukasz.luba@arm.com>

On Tue, Jan 31, 2017 at 04:11:44PM +0000, Lukasz Luba wrote:
> Hi,
> 
> This patchset introduces a new interface for devfreq cooling in thermal
> framework. The previous version of the patch can be seen here [1].
> I have simplified the implementation and introduced resource utilization
> scaling factor.
> 
> The current implementation in the thermal devfreq cooling subsystem uses
> pre-calculated power table for each device to make a decision about allowed
> running state. When the driver registers itself to the thermal devfreq cooling
> subsystem, the framework creates the power table.
> The power table is then used by the thermal subsystem to keep
> the device in the thermal envelope.
> In the previous implementation the pre-calculated device's power
> table was scaled by current 'utilization'
> ('busy_time' and 'total_time' taken from devfreq 'last_status').
> 
> This idea meets the expectations of the devices which know better the actual
> power that they consume (thanks to power counters). When some
> parts/features of the device are not used the power value might be lower,
> while the frequency and utilization are the same.
> 
> The proposed implementation provides possibility to register a driver to
> thermal devfreq cooling subsystem and use the driver's code during the
> calculation of the power in runtime.
> 
> The device driver can still use pre-calculated power table when these new
> functions are not provided (the new extension can co-exist with old
> implementation).
> 
> The first patch contains some refactoring for getting the voltage,
> the second implements the new feature, the third one changes trace function.
> Patchset is based on v4.10-rc5.
> 
> Changes v2: 
> - removed 'flags' and power2state function,
> - split into a few patches,
> - simplified the logic of the new interface,
> - added resource utilization scaling factor,
> 
> Regards,
> Lukasz Luba
> 
> [1] https://marc.info/?l=linux-pm&m=147395070729989&w=2
> 
> 
> Lukasz Luba (3):
>   thermal: devfreq_cooling: refactor code and add get_voltage function
>   thermal: devfreq_cooling: add new interface for direct power read
>   trace: thermal: add another parameter *power to the tracing function
> 

For the series:

Acked-by: Javi Merino <javi.merino@kernel.org>

Thanks!
Javi

  parent reply	other threads:[~2017-02-21 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 16:11 [PATCH v2 0/3] devfreq_cooling: let the driver supply the real power every time we need it Lukasz Luba
2017-01-31 16:11 ` [PATCH v2 1/3] thermal: devfreq_cooling: refactor code and add get_voltage function Lukasz Luba
2017-01-31 16:11 ` [PATCH v2 2/3] thermal: devfreq_cooling: add new interface for direct power read Lukasz Luba
2017-02-21 13:34   ` Javi Merino
2017-01-31 16:11 ` [PATCH v2 3/3] trace: thermal: add another parameter *power to the tracing function Lukasz Luba
2017-02-21 13:35 ` Javi Merino [this message]
2017-02-28 13:52   ` [PATCH v2 0/3] devfreq_cooling: let the driver supply the real power every time we need it Lukasz Luba

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=20170221133559.GC23954@ct-lt-587 \
    --to=javi.merino@kernel.org \
    --cc=chris.diamand@arm.com \
    --cc=edubezval@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=orjan.eide@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