[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpok-ZdxJMCsLMGVA1yhmCjQyTwhCTu7PuXU47wpLQQyxEg@mail.gmail.com>
Date: Thu, 10 Jul 2014 19:43:07 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Borislav Petkov <bp@...en8.de>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Arvind Chauhan <arvind.chauhan@....com>
Subject: Re: [PATCH] cpufreq: report driver's successful {un}registration
On 10 July 2014 19:37, Borislav Petkov <bp@...en8.de> wrote:
> On Thu, Jul 10, 2014 at 05:38:23PM +0530, Viresh Kumar wrote:
>> The problem with that is: CPUFreq may not be compiled in at all and we
>> wouldn't know the difference between success and absence.
>
> Of course you would: /sys/devices/system/cpu/cpufreq/
Yeah, with a local board its easily detectable.
But I faced the issue when I had to see some test reports from
the automated stuff and wanted to see if cpufreq is up and running.
--
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