[lkml]   [2005]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: cpufreq problem wrt suspend/resume on Athlon64

    > On Thu, Feb 03, 2005 at 11:41:26AM +0100, Pavel Machek wrote:
    > > Okay, you are right, restoring it unconditionaly would be bad
    > > idea. Still it would be nice to tell cpufreq governor "please change
    > > the frequency ASAP" so it does not run at 800MHz for half an hour
    > > compiling kernels on AC power.
    > It already does that... or at least it should. in cpufreq_resume() there is
    > a call to schedule_work(&cpu_policy->update); which will cause a call
    > cpufreq_update_policy() in due course. And cpufreq_update_policy() calls the
    > governor, and it is supposed to adjust the frequency to the user's wish
    > then.

    Ok, so Rafael's suspend() routine seems like good fix... Please
    People were complaining that M$ turns users into beta-testers...
    ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:10    [W:0.027 / U:15.888 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site