From: Dominik Brodowski <linux@brodo.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "Mallick, Asit K" <asit.k.mallick@intel.com>,
cpufreq@www.linux.org.uk, "Nakajima,
Jun" <jun.nakajima@intel.com>, linux-acpi <linux-acpi@intel.com>
Subject: Re: [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI P-state driver
Date: Tue, 21 Oct 2003 22:59:13 +0200 [thread overview]
Message-ID: <20031021205913.GK26971@brodo.de> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB60077914@scsmsx403.sc.intel.com>
A few comments on this patch.
> + * Copyright (C) 2001 Russell King
> + * (C) 2002 - 2003 Dominik Brodowski <linux@brodo.de>
As nothing in this driver is from me, please remove my copyright
> + * $Id:$
No need for an ID tag -- you can remove that as well.
> +#define DBS_RATE (HZ/4) /* timer rate is 250ms */
> +#define LOW_LATENCY_FREQUENCY_CHANGE_LIMIT 100 /* in uS */
That's really low. latency_timer is in 10^(-9) s == ns [see cpufreq.h], so I
think you're missing a factor of 1000 here -- but maybe some drivers miss a
factor of 1000, too...
> +static int cpufreq_governor_dbs(struct cpufreq_policy *policy,
> + unsigned int event)
> +{
> + unsigned int cpu = policy->cpu;
> +
> + switch (event) {
> + case CPUFREQ_GOV_START:
> + if ((!cpu_online(cpu)) || (!try_module_get(THIS_MODULE)) || !policy->cur)
> + return -EINVAL;
You needn't worry about try_module_get()/put_module() and friends. That's handled by
the cpufreq core already.
Dominik
next prev parent reply other threads:[~2003-10-21 20:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 2:56 [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI P-state driver Pallipadi, Venkatesh
2003-10-21 8:38 ` Arjan van de Ven
2003-10-21 9:59 ` Mattia Dongili
2003-10-21 10:17 ` Wichert Akkerman
2003-10-21 10:52 ` Mattia Dongili
2003-10-21 12:59 ` Wichert Akkerman
2003-10-21 15:36 ` Daniel Thor Kristjansson
2003-10-21 20:32 ` Dominik Brodowski
2003-10-22 15:48 ` Daniel Thor Kristjansson
2003-10-23 14:32 ` Pavel Machek
2003-10-24 18:22 ` Dominik Brodowski
2003-10-21 19:23 ` Carl Thompson
2003-10-21 20:37 ` Dominik Brodowski
2003-10-21 20:44 ` Dominik Brodowski
2003-10-21 20:59 ` Dominik Brodowski [this message]
2003-10-23 14:17 ` Pavel Machek
2003-10-23 20:47 ` Moore, Robert
2003-10-23 21:50 ` Nakajima, Jun
2003-10-24 18:38 ` Dominik Brodowski
2003-10-24 11:27 ` Ducrot Bruno
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 5:50 Pallipadi, Venkatesh
2003-10-24 18:52 Pallipadi, Venkatesh
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=20031021205913.GK26971@brodo.de \
--to=linux@brodo.de \
--cc=asit.k.mallick@intel.com \
--cc=cpufreq@www.linux.org.uk \
--cc=jun.nakajima@intel.com \
--cc=linux-acpi@intel.com \
--cc=venkatesh.pallipadi@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