[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1f04bbaf-83ae-6351-dbc9-82d27af030e1@arm.com>
Date: Thu, 22 Feb 2018 09:48:06 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Quentin Perret <quentin.perret@....com>
Cc: Sudeep Holla <sudeep.holla@....com>,
ALKML <linux-arm-kernel@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>,
DTML <devicetree@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arnd Bergmann <arnd@...db.de>,
Alexey Klimov <klimov.linux@...il.com>,
linux-pm@...r.kernel.org
Subject: Re: [PATCH v5 19/20] cpufreq: add support for CPU DVFS based on SCMI
message protocol
On 22/02/18 09:04, Quentin Perret wrote:
> Hi Sudeep,
>
> On Monday 12 Feb 2018 at 18:45:23 (+0000), Sudeep Holla wrote:
> [...]
>> +/*
>> + * perf_ops->freq_set is not a synchronous, the actual OPP change will
>> + * happen asynchronously and can get notified if the events are
>> + * subscribed for by the SCMI firmware
>> + */
>> +static int
>> +scmi_cpufreq_set_target(struct cpufreq_policy *policy, unsigned int index)
>> +{
>> + struct scmi_data *priv = policy->driver_data;
>> + struct scmi_perf_ops *perf_ops = handle->perf_ops;
>> + u64 freq = policy->freq_table[index].frequency * 1000;
>> +
>> + return perf_ops->freq_set(handle, priv->domain_id, freq, false);
>> +}
>
> Is arch_set_freq_scale() needed in this function ?
>
Yes indeed, already added locally[1] after Dietmar started the discussion.
--
Regards,
Sudeep
[1] https://git.kernel.org/sudeep.holla/linux/h/for-list/new_arm_scmi
Powered by blists - more mailing lists