All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: linux-pm@vger.kernel.org, Javi Merino <javi.merino@arm.com>,
	Zhang Rui <rui.zhang@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Regard of thermal power allocator's coefficients
Date: Mon, 15 Feb 2016 12:47:51 +0800	[thread overview]
Message-ID: <20160215044751.GA5660@leoy-linaro> (raw)
In-Reply-To: <20160214171217.GA5924@localhost.localdomain>

Hi Eduardo,

Thanks for replying.

On Sun, Feb 14, 2016 at 09:12:19AM -0800, Eduardo Valentin wrote:
> On Sun, Feb 14, 2016 at 07:00:41PM +0800, Leo Yan wrote:

[...]

> > So want to firstly to confirm if should we pass coefficients by using
> > device tree? Is someone working on related work for this?
> 
> We pass the sustainable power, but not the coefficients. IIRC, the IPA
> coefficients were considered (SW) implementation details. Sustainable power,
> on the other hand, still describes hardware capabilities.
> 
> So, I don't think they will go via DT.

I'd like clarify one thing: "coefficients" are used to calculate
static leakage and dynamic power but not PID's term constants. They
are quite dependent on silicon's process; this is similiar with
sustainable power. So do you think we should take these "coefficients"
as software paramters?

The code is written in drivers/thermal/hisi_thermal.c like below:

---8<---

struct cluster_power_coefficients cluster_data = {
	.dyn_coeff      = 266,
	.static_cpu     = 14,
	.static_cluster = 5,
};

/* voltage in uV and temperature in mC */
static int get_static_power(cpumask_t *cpumask, int interval,
		unsigned long u_volt, u32 *power)
{
	int nr_cpus = cpumask_weight(cpumask);

	*power  = nr_cpus * cluster_data.static_cpu;
	*power += 2 * cluster_data.static_cluster;

	return 0;
}

static int hisi_thermal_register_cooling_device(struct platform_device *pdev,
						struct hisi_thermal_data *data)
{
	struct device_node *np;

	np = of_find_node_by_name(NULL, "cluster0");
	if (!np) {
		dev_err(&pdev->dev, "Cluster0 node not founds\n");
		return -ENODEV;
	}

	data->cdevs = of_cpufreq_power_cooling_register(np,
			cpu_present_mask, cluster_data.dyn_coeff,
			get_static_power);
	if (IS_ERR(data->cdevs)) {
		dev_err(&pdev->dev,
			"Error registering cooling device: %ld\n",
			PTR_ERR(data->cdevs));
		return PTR_ERR(data->cdevs);
	}

	return 0;
}

Thanks,
Leo Yan

  reply	other threads:[~2016-02-15  4:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 11:00 Regard of thermal power allocator's coefficients Leo Yan
2016-02-14 17:12 ` Eduardo Valentin
2016-02-15  4:47   ` Leo Yan [this message]
2016-02-18 15:19     ` Javi Merino
2016-02-19  9:03       ` Leo Yan

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=20160215044751.GA5660@leoy-linaro \
    --to=leo.yan@linaro.org \
    --cc=edubezval@gmail.com \
    --cc=javi.merino@arm.com \
    --cc=linux-kernel@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 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.