mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas, Sujith" <sujith.thomas@intel.com>
To: "Len Brown" <lenb@kernel.org>, "Zhang, Rui" <rui.zhang@intel.com>,
	"Thomas, Sujith" <sujith.thomas@intel.com>
Cc: "Brown, Len" <len.brown@intel.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	<linux-acpi@vger.kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: [PATCH]1/3 intel_menlow:Adding comment for GTHS legal values
Date: Wed, 5 Nov 2008 16:15:13 +0530	[thread overview]
Message-ID: <7D0189F5BE1DF549A570B212D1D5612182AF02@bgsmsx412.gar.corp.intel.com> (raw)

Documentation of legal values for GTHS
To be patched over Rui's 09/11 bug fix patch

Signed-off-by: Sujith Thomas <sujith.thomas@intel.com>
---
 drivers/misc/intel_menlow.c |    5 +++++
 1 file changed, 5 insertions(+)

Index: linux-2.6.27/drivers/misc/intel_menlow.c
===================================================================
--- linux-2.6.27.orig/drivers/misc/intel_menlow.c
+++ linux-2.6.27/drivers/misc/intel_menlow.c
@@ -52,6 +52,11 @@ MODULE_LICENSE("GPL");
 #define MEMORY_ARG_CUR_BANDWIDTH 1
 #define MEMORY_ARG_MAX_BANDWIDTH 0
 
+/*
+ * GTHS returning 'n' would mean that [0,n-1] states are supported
+ * In that case max_cstate would be n-1
+ * GTHS returning '0' would mean that no bandwidth control states are
supported
+ */
 static int memory_get_int_max_bandwidth(struct thermal_cooling_device
*cdev,
 					unsigned long *max_state)
 {

             reply	other threads:[~2008-11-05 10:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 10:45 Thomas, Sujith [this message]
2008-11-06 23:47 ` Andrew Morton
2008-11-07  1:35 ` Len Brown

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=7D0189F5BE1DF549A570B212D1D5612182AF02@bgsmsx412.gar.corp.intel.com \
    --to=sujith.thomas@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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

all inboxes | Powered by JetHome®