All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 10062] cpufreq scaling for via c3 no longer works
Date: Sun,  1 Jun 2008 18:53:29 -0700 (PDT)	[thread overview]
Message-ID: <20080602015329.8CBBA108035@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-10062-3570@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=10062


protasnb@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |protasnb@gmail.com,
                   |                            |rafalbilski@interia.pl




------- Comment #3 from protasnb@gmail.com  2008-06-01 18:53 -------
There was a commit that tried to deal with longhaul erratas:
commit 52a2638bff063acb28ba3355891c49cc240cc98b
Author: Rafal Bilski <rafalbilski@interia.pl>
Date:   Sun Oct 7 00:24:32 2007 -0700

    Longhaul: add auto enabled "revid_errata" option

    VIA C3 Ezra-T has RevisionID equal to 1, but it needs RevisionKey to be 0
    or CPU will ignore new frequency and will continue to work at old
    frequency.  New "revid_errata" option will force RevisionKey to be set to
    0, whatever RevisionID is.

    Additionaly "Longhaul" will not silently ignore unsuccessful transition.
    It will try to check if "revid_errata" or "disable_acpi_c3" options need to
    be enabled for this processor/system.

    Same for Longhaul ver.  2 support.  It will be disabled if none of above
    options will work.

     Best case scenario (with patch apllied and v2 enabled):
     longhaul: VIA C3 'Ezra' [C5C] CPU detected.  Longhaul v2 supported.
     longhaul: Using northbridge support.
     longhaul: VRM 8.5
     longhaul: Max VID=1.350  Min VID=1.050, 13 possible voltage scales
     longhaul: f: 300000 kHz, index: 0, vid: 1050 mV
     [...]
     longhaul: Voltage scaling enabled.
     Worst case scenario:
     longhaul: VIA C3 'Ezra-T' [C5M] CPU detected.  Powersaver supported.
     longhaul: Using northbridge support.
     longhaul: Using ACPI support.
     longhaul: VRM 8.5
     longhaul: Claims to support voltage scaling but min & max are both 1.250.
Voltage scaling disabled
     longhaul: Failed to set requested frequency!
     longhaul: Enabling "Ignore Revision ID" option.
     longhaul: Failed to set requested frequency!
     longhaul: Disabling ACPI C3 support.
     longhaul: Disabling "Ignore Revision ID" option.
     longhaul: Failed to set requested frequency!
     longhaul: Enabling "Ignore Revision ID" option.

You can enable CPU_FREQ_DEBUG and place cpufreq.debug=2 for driver debug on the
boot command line.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

      parent reply	other threads:[~2008-06-02  1:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 23:27 [Bug 10062] New: cpufreq scaling for via c3 no longer works bugme-daemon
2008-02-25 21:54 ` [Bug 10062] " bugme-daemon
2008-03-07 11:34 ` bugme-daemon
2008-06-02  1:53 ` bugme-daemon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080602015329.8CBBA108035@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=cpufreq@www.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.