From: Greg KH <greg@kroah.com>
To: Daniel Pittman <daniel@rimspace.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CPUFreq sysfs interface MIA?
Date: Wed, 7 May 2003 16:32:57 -0700 [thread overview]
Message-ID: <20030507233257.GA4481@kroah.com> (raw)
In-Reply-To: <87n0hzbnk6.fsf@enki.rimspace.net>
On Wed, May 07, 2003 at 10:36:09AM +1000, Daniel Pittman wrote:
> On Tue, 6 May 2003, Greg KH wrote:
> > On Tue, May 06, 2003 at 05:29:15PM +1000, Daniel Pittman wrote:
> >>
> >> The content of /sys/devices/sys/cpu0 is:
> >> /sys/devices/sys/cpu0
> >> |-- name
> >> `-- power
> >
> > What does /sys/class/cpu show?
>
> /sys/class/cpu
> `-- cpu0
> `-- device -> ../../../devices/sys/cpu0
Oops, forgot to hook up stuff... Does the following patch from Jonathan
Corbet fix this?
thanks,
greg k-h
# cpufreq class fix
diff -Nru a/include/linux/cpu.h b/include/linux/cpu.h
--- a/include/linux/cpu.h Wed May 7 16:29:37 2003
+++ b/include/linux/cpu.h Wed May 7 16:29:37 2003
@@ -29,6 +29,7 @@
};
extern int register_cpu(struct cpu *, int, struct node *);
+extern struct class cpu_class;
/* Stop CPUs going up and down. */
extern struct semaphore cpucontrol;
diff -Nru a/kernel/cpufreq.c b/kernel/cpufreq.c
--- a/kernel/cpufreq.c Wed May 7 16:29:37 2003
+++ b/kernel/cpufreq.c Wed May 7 16:29:37 2003
@@ -22,6 +22,7 @@
#include <linux/spinlock.h>
#include <linux/device.h>
#include <linux/slab.h>
+#include <linux/cpu.h>
/**
* The "cpufreq driver" - the arch- or hardware-dependend low
@@ -115,6 +116,7 @@
extern struct device_class cpu_devclass;
static struct class_interface cpufreq_interface = {
+ .class = &cpu_class,
.add = &cpufreq_add_dev,
.remove = &cpufreq_remove_dev,
};
next prev parent reply other threads:[~2003-05-07 23:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 7:29 CPUFreq sysfs interface MIA? Daniel Pittman
2003-05-06 21:12 ` Greg KH
2003-05-07 0:36 ` Daniel Pittman
2003-05-07 23:32 ` Greg KH [this message]
2003-05-08 0:23 ` Daniel Pittman
2003-05-08 0:32 ` Greg KH
2003-05-08 2:02 ` Daniel Pittman
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=20030507233257.GA4481@kroah.com \
--to=greg@kroah.com \
--cc=daniel@rimspace.net \
--cc=linux-kernel@vger.kernel.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