On 3 December 2013 04:03, Rafael J. Wysocki wrote:
> On Monday, December 02, 2013 07:23:01 AM Dirk Brandewie wrote:
>> Sorry for late response to these threads. Holiday weekend in the US.
No issues.
>> NAK for intel_pstate. The code that will use this flag also uses
>> has_target()
>> which i
On Monday, December 02, 2013 07:23:01 AM Dirk Brandewie wrote:
> Sorry for late response to these threads. Holiday weekend in the US.
>
> On 11/29/2013 06:14 AM, Viresh Kumar wrote:
> > On some systems we can't really say what frequency we're running at the
> > moment
> > and so for these we sho
Sorry for late response to these threads. Holiday weekend in the US.
On 11/29/2013 06:14 AM, Viresh Kumar wrote:
On some systems we can't really say what frequency we're running at the moment
and so for these we shouldn't check if we are running at a frequency present in
frequency table. For no
On some systems we can't really say what frequency we're running at the moment
and so for these we shouldn't check if we are running at a frequency present in
frequency table. For now mark all x86 drivers with this flag:
CPUFREQ_SKIP_INITIAL_FREQ_CHECK.
This patch also defines this macro. It will
4 matches
Mail list logo
