On 11 October 2016 at 22:38, Viresh Kumar wrote:
> On 07-10-16, 16:21, Markus Mayer wrote:
>> +static int brcm_avs_cpufreq_exit(struct cpufreq_policy *policy)
>> +{
>> + struct private_data *priv = policy->driver_data;
>> +
>> + iounmap(priv->base);
>> + iounmap(priv->avs_intr_base);
>
On 07-10-16, 16:21, Markus Mayer wrote:
> +static int brcm_avs_cpufreq_exit(struct cpufreq_policy *policy)
> +{
> + struct private_data *priv = policy->driver_data;
> +
> + iounmap(priv->base);
> + iounmap(priv->avs_intr_base);
> +
> + return 0;
> +}
Shouldn't the above be done in
This driver supports voltage and frequency scaling on Broadcom STB SoCs
using AVS firmware with DFS and DVFS support.
Actual frequency or voltage scaling is done exclusively by the AVS
firmware. The driver merely provides a standard CPUfreq interface to
other kernel components and userland, and in
3 matches
Mail list logo