From: Dave Jones <davej@redhat.com>
To: "Leisner, Martin" <Martin.Leisner@xerox.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: writing a frequency scaling processor module
Date: Mon, 24 Sep 2007 19:31:35 -0400 [thread overview]
Message-ID: <20070924233135.GK8127@redhat.com> (raw)
In-Reply-To: <556445368AFA1C438794ABDA8901891C066B5BD9@USA0300MS03.na.xerox.net>
On Fri, Sep 07, 2007 at 01:04:51PM -0400, Leisner, Martin wrote:
> I'm writing a cpufreq module for the ppc 7448 processor.
>
> Its very nice the way cpufreq is laid out with the governors...is there
> a
> "cookbook" approach to writing a processor interface?
Not really. Rumour has it that kernel programmers hate writing
documentation ;^)
> I looked at cpu-drivers.txt in the kernel tree, and it's somewhat vague
> and confusing (IMHO).
>
> I'm using p4-clocmod.c as an example, are there better examples?
that, longhaul and powernow-k7 are fairly simple to understand.
Is there anything in particular you have problems understanding ?
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-09-24 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 17:04 writing a frequency scaling processor module Leisner, Martin
2007-09-24 23:31 ` Dave Jones [this message]
2007-09-25 16:48 ` Leisner, Martin
2007-09-25 17:02 ` Dave Jones
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=20070924233135.GK8127@redhat.com \
--to=davej@redhat.com \
--cc=Martin.Leisner@xerox.com \
--cc=cpufreq@lists.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 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.