From: Pavel Machek <pavel@ucw.cz>
To: David Singleton <daviado@gmail.com>
Cc: Greg KH <greg@kroah.com>,
linux-pm@lists.osdl.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: OpPoint summary
Date: Sun, 17 Sep 2006 19:48:35 +0200 [thread overview]
Message-ID: <20060917174835.GA2225@elf.ucw.cz> (raw)
In-Reply-To: <b324b5ad0609141007i2a26cf60r45ebf1175c7bcc7d@mail.gmail.com>
Hi!
> >Care to resend your patches in the proper format, through email so that
> >we can see them, and possibly get some testing in -mm if they look sane?
>
> Greg,
> here's the patch that implements operating points for different
> frequencies
> for the speedstep-centrino line of processors. Operating points are created
> in much the same manner that cpufreq tables are. This works for both
> simple implementations like the centrino and more complex SoC systems
> like the arm-pxa72x which has several clocks to control, and different clock
> divisors and multipliers.
> +static struct oppoint lowest = {
> + .name = "lowest",
> + .type = PM_FREQ_CHANGE,
> + .frequency = 0,
> + .voltage = 0,
> + .latency = 15,
> + .prepare_transition = cpufreq_prepare_transition,
> + .transition = centrino_transition,
> + .finish_transition = cpufreq_finish_transition,
> +};
We had nice, descriptive interface... with numbers. Now you want to
introduce english state names... looks like a step back to me.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-09-17 21:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <450516E8.9010403@gmail.com>
[not found] ` <20060911082025.GD1898@elf.ucw.cz>
[not found] ` <b0623b9bb79afacc77cddc6e39c96b62@nomadgs.com>
[not found] ` <20060911195546.GB11901@elf.ucw.cz>
[not found] ` <4505CCDA.8020501@gmail.com>
[not found] ` <20060911210026.GG11901@elf.ucw.cz>
[not found] ` <4505DDA6.8080603@gmail.com>
2006-09-11 22:56 ` cpufreq terminally broken [was Re: community PM requirements/issues and PowerOP] Pavel Machek
2006-09-12 0:17 ` Mark Gross
2006-09-12 3:37 ` Greg KH
2006-09-13 23:50 ` [linux-pm] " David Singleton
2006-09-14 5:30 ` Vitaly Wool
2006-09-14 5:55 ` OpPoint summary Greg KH
2006-09-14 7:35 ` [linux-pm] " Vitaly Wool
2006-09-14 16:55 ` David Singleton
2006-09-14 17:03 ` David Singleton
2006-09-14 17:07 ` David Singleton
2006-09-14 17:25 ` Auke Kok
2006-09-14 18:15 ` [linux-pm] " Vitaly Wool
2006-09-14 18:17 ` David Singleton
2006-09-17 17:48 ` Pavel Machek [this message]
2006-09-18 14:33 ` [linux-pm] " Richard A. Griffiths
2006-09-18 16:13 ` Matthew Locke
2006-09-14 17:11 ` David Singleton
2006-09-17 5:07 ` David Singleton
2006-09-17 12:56 ` Pavel Machek
2006-09-17 12:58 ` Pavel Machek
2006-09-17 22:43 ` [linux-pm] " Matthew Locke
2006-09-12 8:33 ` cpufreq terminally broken [was Re: community PM requirements/issues and PowerOP] Pavel Machek
2006-09-12 9:10 ` [linux-pm] " Vitaly Wool
2006-09-12 9:16 ` Pavel Machek
2006-09-12 9:23 ` Vitaly Wool
2006-09-14 15:04 ` Mark Gross
2006-09-14 14:58 ` Mark Gross
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=20060917174835.GA2225@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=daviado@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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
Powered by JetHome