From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] cpufreq: scpi: remove arm_big_little dependency
Date: Wed, 10 Jan 2018 09:49:05 +0530 [thread overview]
Message-ID: <20180110041905.GC3335@vireshk-i7> (raw)
In-Reply-To: <1515516568-31359-3-git-send-email-sudeep.holla@arm.com>
On 09-01-18, 16:49, Sudeep Holla wrote:
> +static int
> +scpi_get_sharing_cpus(struct device *cpu_dev, struct cpumask *cpumask)
> {
> - return scpi_ops->get_transition_latency(cpu_dev);
> + int cpu, domain, tdomain;
> + struct device *tcpu_dev;
> +
> + domain = scpi_ops->device_domain_id(cpu_dev);
> + if (domain < 0)
> + return domain;
> +
> + for_each_possible_cpu(cpu) {
> + if (cpu == cpu_dev->id)
> + continue;
> +
> + tcpu_dev = get_cpu_device(cpu);
> + if (!tcpu_dev)
> + continue;
> +
> + tdomain = scpi_ops->device_domain_id(tcpu_dev);
> + if (tdomain == domain)
> + cpumask_set_cpu(cpu, cpumask);
> + }
> +
> + return 0;
> }
So this is the main thing you want to achieve ? i.e. get the
policy->cpus from scpi_ops, right ?
Why can't we update .init_opp_table() to include policy as a parameter
and let individual stub drivers update policy->cpus then ?
--
viresh
next prev parent reply other threads:[~2018-01-10 4:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 16:49 [PATCH 0/2] drivers: remove incorrect usage/dependency on topology_physical_package_id Sudeep Holla
2018-01-09 16:49 ` [PATCH 1/2] drivers: psci: remove cluster terminology and dependency on physical_package_id Sudeep Holla
2018-01-09 17:34 ` Lorenzo Pieralisi
2018-01-09 18:42 ` Sudeep Holla
2018-01-09 16:49 ` [PATCH 2/2] cpufreq: scpi: remove arm_big_little dependency Sudeep Holla
2018-01-10 4:19 ` Viresh Kumar [this message]
2018-01-10 11:34 ` Sudeep Holla
2018-01-10 14:46 ` Viresh Kumar
2018-01-10 16:45 ` Sudeep Holla
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=20180110041905.GC3335@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).