public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Alex <ambroxa@yahoo.it>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Avoid C2/C3 idle state
Date: Wed, 25 Nov 2009 09:05:37 +0100	[thread overview]
Message-ID: <20091125080537.GA31368@isilmar.linta.de> (raw)
In-Reply-To: <796045.7445.qm@web26501.mail.ukl.yahoo.com>

On Wed, Nov 25, 2009 at 06:53:14AM +0000, Alex wrote:
> --- Mar 24/11/09, Dominik Brodowski <linux@dominikbrodowski.net> ha scritto:
> 
> > Da: Dominik Brodowski <linux@dominikbrodowski.net>
> > Oggetto: Re: Avoid C2/C3 idle state
> > A: "Alex" <ambroxa@yahoo.it>
> > Cc: linux-acpi@vger.kernel.org
> > Data: Martedì 24 novembre 2009, 23:29
> > Hey,
> > 
> > you can set the maximum C-state to use using the
> > "processor.max_cstate=<value>" parameter. No need to
> > recompile.
> 
> Thanks for your kind reply.
> 
> A stupid qustion:
> <value> is a numeric value as 1 , 2 , 3  (i.e. processor.max_cstate=1 )
> or is a string like C1 , C2 , C3 (i.e. processor.max_cstate=C1 ) ?

It's the former. I'd suggest you try max_cstate=2 first, as that might save
power, reduce heat and still not interfere with the serial device.

Best,
	Dominik
--
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

  reply	other threads:[~2009-11-25  8:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 21:50 Avoid C2/C3 idle state Alex
2009-11-24 22:29 ` Dominik Brodowski
2009-11-25  6:53   ` Alex
2009-11-25  8:05     ` Dominik Brodowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-11-25 12:05 Alex

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=20091125080537.GA31368@isilmar.linta.de \
    --to=linux@dominikbrodowski.net \
    --cc=ambroxa@yahoo.it \
    --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