cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot@arm.linux.org.uk>
To: cpufreq@lists.arm.linux.org.uk
Subject: cpufreq/linux/include/linux cpufreq.h,1.44,1.45
Date: Wed, 03 Sep 2003 10:20:04 +0100	[thread overview]
Message-ID: <E19uTo4-0005du-Rl@flint.arm.linux.org.uk> (raw)

Update of /mnt/src/cvsroot/cpufreq/linux/include/linux
In directory flint:/tmp/cvs-serv21659/linux/include/linux

Modified Files:
	cpufreq.h 
Log Message:
* add speedstep-smi driver (Hiroshi Miura)
* clean up speedstep-smi driver (Dominik Brodowski)
        - fixes a couple of warnings
        - to run as a module, we need to export ist_info. Also, only show the
          IST_INFO line in dmesg if speedstep_smi is enabled.
        - Use  a new ->resume callback in the cpufreq core.
        - let's call this driver "speedstep-smi" in cpufreq_driver also
        - if the smi_get_freqs call fails, fall back to the "let's try it out
          and see what frequency we are at" mechanism. Needed on my notebook (at
          least).
* update driver/cpufreq/cpufreq.c


Index: cpufreq.h
===================================================================
RCS file: /mnt/src/cvsroot/cpufreq/linux/include/linux/cpufreq.h,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- cpufreq.h	19 Aug 2003 13:38:33 -0000	1.44
+++ cpufreq.h	3 Sep 2003 09:20:00 -0000	1.45
@@ -176,6 +176,7 @@
 
 	/* optional */
 	int	(*exit)		(struct cpufreq_policy *policy);
+	int	(*resume)	(struct cpufreq_policy *policy);
 	struct freq_attr	**attr;
 };

                 reply	other threads:[~2003-09-03  9:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E19uTo4-0005du-Rl@flint.arm.linux.org.uk \
    --to=ducrot@arm.linux.org.uk \
    --cc=cpufreq@lists.arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox