[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 5 May 2014 19:53:14 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Nishanth Menon <nm@...com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Kevin Hilman <khilman@...prootsystems.com>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
linux-omap <linux-omap@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] PM / OPP: Remove cpufreq wrapper dependency on
internal data organization
On 5 May 2014 19:03, Nishanth Menon <nm@...com> wrote:
> diff --git a/drivers/base/power/opp.c b/drivers/base/power/opp.c
> int dev_pm_opp_init_cpufreq_table(struct device *dev,
> struct cpufreq_frequency_table **table)
> {
> - struct device_opp *dev_opp;
> struct dev_pm_opp *opp;
> - struct cpufreq_frequency_table *freq_table;
> - int i = 0;
> + struct cpufreq_frequency_table *freq_table = NULL;
> + int i, max_opps, ret = 0;
> + unsigned long rate;
>
> - /* Pretend as if I am an updater */
> - mutex_lock(&dev_opp_list_lock);
What if opp is being added for some reason at the same time?
I hope we can surely see some awkward results, maybe some
NULL pointers invocations as well..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists