From: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
To: Balaji Rao <balajirrao@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Power States
Date: Wed, 20 Dec 2006 22:14:29 +0300 [thread overview]
Message-ID: <45898B95.2020007@linux.intel.com> (raw)
In-Reply-To: <569c97d20612201109i7c8d3accl6ac2346ba023401b@mail.gmail.com>
6 is lowest FSB multiplier, 0.266*6 = 1.6GHz -- your lowest.
7 is multiplier to get 1.86Ghz -- your max.
"power management: no" means power management is disabled.
Balaji Rao wrote:
> also, the file cat /proc/acpi/processor/CPU1/info gives this
>
> processor id: 0
> acpi id: 1
> bus mastering control: yes
> power management: no
> throttling control: yes
> limit interface: yes
>
> Is power management not available according to this file?
>
> One more thing is that, only two frequency levels ( 1.86 and 1.6 Ghz)
> are being used. This does not cause much power saving..
>
> How many levels are actually available on core 2 duo?
>
> I cant find any PSS in the DSDT dump.
>
> On 12/21/06, Alexey Starikovskiy
> <alexey.y.starikovskiy@linux.intel.com> wrote:
>> Then you should check your BIOS settings for DBS/EST/speedstep etc
>> support.
>> C1 is the only C-state supported on CoreDuo2.
>> PSS should give you P-states.
>>
>> Balaji Rao wrote:
>> > But, acpidump doest give me anything saying SSDT..
>> > Actually the problem is, only one power state(C1) is being shown up in
>> > my Core 2 Duo (E6300) box.
>> >
>> > Also, power management is reported as not available.
>> >
>> > Where can i look for a solution?
>> >
>> >
>> > On 12/21/06, Alexey Starikovskiy
>> > <alexey.y.starikovskiy@linux.intel.com> wrote:
>> >> Balaji Rao wrote:
>> >> > Hello all,
>> >> >
>> >> > Are the various power levels supported by the processor provided
>> only
>> >> > through the DSDT? Or is there any other table for this purpose?
>> >> > When i disassembled my DSDT, i could not find any _PSS Packages.
>> >> >
>> >> > From where does the kernel read values into the frequency table?
>> >> >
>> >> > Also, which is the mechanism that decides to load the appropriate
>> >> > cpufreq driver?
>> >> >
>> >> > warm regards
>> >> >
>> >> > Balaji Rao
>> >> > -
>> >> > To unsubscribe from this list: send the line "unsubscribe
>> >> linux-acpi" in
>> >> > the body of a message to majordomo@vger.kernel.org
>> >> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>> >> Check SSDTs as well.
>> >>
>> >> Regards,
>> >> Alex.
>> >>
>> >
>> >
>>
>
>
next prev parent reply other threads:[~2006-12-20 19:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 18:33 Power States Balaji Rao
2006-12-20 18:35 ` Alexey Starikovskiy
2006-12-20 18:51 ` Balaji Rao
2006-12-20 19:01 ` Alexey Starikovskiy
2006-12-20 19:09 ` Balaji Rao
2006-12-20 19:14 ` Alexey Starikovskiy [this message]
2006-12-20 19:20 ` Balaji Rao
2006-12-20 19:56 ` Alexey Starikovskiy
2006-12-21 17:02 ` Balaji Rao
2006-12-21 9:28 ` Zhang Rui
2006-12-21 13:36 ` Lincoln Baxter, III
2006-12-21 17:00 ` Balaji Rao
2006-12-21 7:33 ` Oliver Henriot
2006-12-21 7:09 ` Oliver Henriot
2006-12-21 7:16 ` Oliver Henriot
2006-12-21 17:00 ` Balaji Rao
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=45898B95.2020007@linux.intel.com \
--to=alexey.y.starikovskiy@linux.intel.com \
--cc=balajirrao@gmail.com \
--cc=linux-acpi@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox