From: Dave Jones <davej@redhat.com>
To: Ryan Underwood <nemesis@icequake.net>
Cc: Cpufreq@lists.linux.org.uk
Subject: Re: writing a cpufreq driver
Date: Thu, 21 Sep 2006 17:13:43 -0400 [thread overview]
Message-ID: <20060921211343.GG26683@redhat.com> (raw)
In-Reply-To: <20060921210329.GA16590@dbz.icequake.net>
On Thu, Sep 21, 2006 at 04:03:29PM -0500, Ryan Underwood wrote:
>
> On Thu, Sep 21, 2006 at 04:44:02PM -0400, Dave Jones wrote:
> > >
> > > No, because only the firmware knows what the real CPU speeds are. How
> > > would I deal with this?
> >
> > Actually, if your driver is correctly using cpufreq_notify_transition()
> > it should be doing this automagically for you. If you turn on debugging with
> > cpufreq.debug=7 , you should see lines of the form.
> >
> > scaling loops_per_jiffy to %lu for frequency %u kHz\n
>
> I don't see this, here's the dmesg (2.6.16.28)
Pointer to the driver source ?
Dave
next prev parent reply other threads:[~2006-09-21 21:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 18:48 writing a cpufreq driver Ryan Underwood
2006-09-21 19:31 ` Dave Jones
2006-09-21 19:38 ` Langsdorf, Mark
2006-09-21 19:47 ` Dave Jones
2006-09-22 15:44 ` Bruno Ducrot
2006-09-22 15:49 ` Dave Jones
2006-09-21 20:08 ` Ryan Underwood
2006-09-21 20:44 ` Dave Jones
2006-09-21 21:03 ` Ryan Underwood
2006-09-21 21:13 ` Dave Jones [this message]
2006-09-22 14:13 ` Ryan Underwood
2006-09-22 14:39 ` Ryan Underwood
2006-09-22 15:48 ` Bruno Ducrot
2006-09-22 16:01 ` Ryan Underwood
2006-09-22 15:51 ` Dave Jones
2006-09-22 15:39 ` Bruno Ducrot
2006-09-22 16:00 ` Ryan Underwood
2006-09-22 16:05 ` Bruno Ducrot
2006-09-22 16:11 ` Ryan Underwood
2006-09-23 15:07 ` Bruno Ducrot
2006-09-23 15:21 ` Ryan Underwood
2006-09-23 15:44 ` Bruno Ducrot
2006-09-23 16:03 ` Ryan Underwood
2006-09-23 16:13 ` Bruno Ducrot
2006-09-25 15:39 ` Ryan Underwood
2006-10-02 2:19 ` Dominik Brodowski
2006-09-25 16:44 ` Ryan Underwood
-- strict thread matches above, loose matches on Subject: below --
2006-09-22 16:31 Erik Slagter
2006-09-23 15:31 ` Bruno Ducrot
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=20060921211343.GG26683@redhat.com \
--to=davej@redhat.com \
--cc=Cpufreq@lists.linux.org.uk \
--cc=nemesis@icequake.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.