preliminary 750GX PLL control patch
Subsystems (2)
Hi,
I've attached a patch that adds preliminary access to the HID1
register in the 750GX (aka the PLL config register). The patch is against 2.4.30. It has been lightly tested on a PowerMac 8600 with a PowerLogix PowerForce 750GX cpu card.
Depending on the values for the pllx_cfg field, this should
work on the 750FX as well ... except for the stuff in idle_6xx.S. Since there are plenty of people on this list way more smarterer than me I was hoping someone could answer a question about the powersave modes that some of the PowerPC processors have:
Since, as I understand it, the clock is shut off to much of the
chip when a powersave mode is engaged does it really buy you that much to switch to a lower clock speed? Wouldn't you be better off shutting off the unused PLL?
Also, please note that I am not very experienced creating
patches so please use a backup of your source tree.
kevin
Documentation/Configure.help +5 -0
@@ -24304,6 +24304,11 @@ a lot, or the TAU hardware is broken (likely on some G4's). If the range is small (around 4 degrees), the temperature is relatively stable. +Dual PLL support +CONFIG_DUAL_PLL + This option enables sysctl support for checking and modifying the PLLs in + the IBM 750FX and 750GX processors. + Power management support for PowerBooks CONFIG_PMAC_PBOOK This provides support for putting a PowerBook to sleep; it also
arch/ppc/config.in +5 -3
@@ -175,10 +175,12 @@ bool ' Average high and low temp' CONFIG_TAU_AVERAGE fi define_bool CONFIG_PPC_ISATIMER y + + bool 'Dual PLL Support (750FX/GX)' CONFIG_DUAL_PLL fi -if [ "$CONFIG_POWER4" = "y" ]; then - bool 'VMX (same as AltiVec) support' CONFIG_ALTIVEC -fi +#if [ "$CONFIG_POWER4" = "y" ]; then +# bool 'VMX (same as AltiVec) support' CONFIG_ALTIVEC +#fi if [ "$CONFIG_4xx" = "y" -o "$CONFIG_8xx" = "y" ]; then bool 'Math emulation' CONFIG_MATH_EMULATION
arch/ppc/kernel/Makefile +3 -0
@@ -50,6 +50,7 @@ obj-$(CONFIG_PPCBUG_NVRAM) += prep_nvram.o obj-$(CONFIG_SMP) += smp.o obj-$(CONFIG_TAU) += temp.o +obj-$(CONFIG_DUAL_PLL) += pll.o pll_init.o ifeq ($(CONFIG_SERIAL)$(CONFIG_GEN550),yy) obj-$(CONFIG_KGDB) += gen550_kgdb.o gen550_dbg.o obj-$(CONFIG_SERIAL_TEXT_DEBUG) += gen550_dbg.o
@@ -97,6 +98,8 @@ entry.o: entry.S ppc_defs.h misc.o: misc.S ppc_defs.h l2cr.o: l2cr.S ppc_defs.h +pll.o: pll.S ppc_defs.h +pll_init.o: pll_init.c ppc_defs.h head.o: head.S ppc_defs.h head_4xx.o: head_4xx.S ppc_defs.h head_44x.o: head_44x.S ppc_defs.h
arch/ppc/kernel/cpu_setup_6xx.S +12 -0
@@ -48,6 +48,13 @@ bl setup_750fx mtlr r4 blr +_GLOBAL(__setup_cpu_750gx) + mflr r4 + bl setup_common_caches + bl setup_750_7400_hid0 + bl setup_750gx + mtlr r4 + blr _GLOBAL(__setup_cpu_7400) mflr r4 bl setup_7400_workarounds
@@ -200,6 +207,11 @@ /* 750fx specific */ setup_750fx: + blr + +/* 750gx specific + */ +setup_750gx: blr /* MPC 745x
arch/ppc/kernel/cputable.c +48 -3
84 lines not on this page · raw message
arch/ppc/kernel/pll.S +182 -0
182 lines not on this page · raw message
arch/ppc/kernel/pll_init.c +506 -0
506 lines not on this page · raw message
arch/ppc/kernel/ppc_htab.c +18 -5
@@ -510,7 +510,15 @@ left -= len;_set_L2CR (val); }else { -int is750fx = cur_cpu_spec[0 ]->cpu_features &CPU_FTR_750FX ; +int is750fgx = cur_cpu_spec[0 ]->cpu_features & + (CPU_FTR_750FX |CPU_FTR_750GX ); + +/* +* For identifying memory size +*/ +if (is750fgx) is750fgx=(cur_cpu_spec[0 ]->cpu_features + &CPU_FTR_750GX )?3 :2 ; + p = buf;if (!first) *p++ ='\t' ;
@@ -520,7 +528,7 @@ "disabled");if (!(val>>30 &1 )) p +=sprintf (p,"no " ); -if (is750fx) +if (is750fgx) p +=sprintf (p,"ECC checkstop" );else p +=sprintf (p,"parity" );
@@ -528,7 +536,7 @@/* 75x & 74x0 have different L2CR than 745x */ if (!(cur_cpu_spec[0 ]->cpu_features &CPU_FTR_SPEC7450 )) { -if (!is750fx) { +if (!is750fgx) { p +=sprintf (p,", %s" , sizestrings[(val >>28 ) &3 ]); p += sprintf(p, ", %s",
@@ -536,9 +544,14 @@ p +=sprintf (p,", %s" , typestrings[(val >>23 ) &3 ]); } +else + p +=sprintf (p,", %s, +1 clock, " +"on chip, " ,sizestrings[ + is750fgx]); + p +=sprintf (p,"%s" , (val>>22 )&1 ?", data only" :"" ); -if (!is750fx) { +if (!is750fgx) { p +=sprintf (p,"%s" , (val>>20 )&1 ?", ZZ enabled" :"" ); }
@@ -546,7 +559,7 @@ "write-through" : "copy-back"); p +=sprintf (p,"%s" , (val>>18 )&1 ?", testing" :"" ); -if (!is750fx) { +if (!is750fgx) { p +=sprintf (p,", %sns hold" , holdstrings[(val>>16 )&3 ]); p += sprintf(p, "%s", (val>>15)&1 ?
include/asm-ppc/cputable.h +2 -0
@@ -76,6 +76,8 @@#define CPU_FTR_NO_DPM 0x00008000#define CPU_FTR_HAS_HIGH_BATS 0x00010000#define CPU_FTR_NEED_COHERENT 0x00020000 +#define CPU_FTR_750GX 0x00040000 +#define CPU_FTR_DUALPLL 0x00080000#ifdef __ASSEMBLY__
include/asm-ppc/pll.h +125 -0
125 lines not on this page · raw message
include/linux/sysctl.h +1 -0
@@ -128,6 +128,7 @@KERN_PPC_L3CR =57 ,/* l3cr register on PPC */ KERN_EXCEPTION_TRACE =58 ,/* boolean: exception trace */ KERN_CORE_SETUID =59 ,/* int: set to allow core dumps of setuid apps */ +KERN_PPC_PLL =60 ,/* PLL control register (HID1) on some PPC */ KERN_SPARC_SCONS_PWROFF=64, /* int: serial console power-off halt */ };
kernel/sysctl.c +6 -0
@@ -100,6 +100,8 @@ void *buffer, size_t *lenp);int proc_dol3crvec (ctl_table *table,int write,struct file *filp,void *buffer,size_t *lenp); +int proc_dopllvec (ctl_table *table,int write,struct file *filp, +void *buffer,size_t *lenp);#endif #ifdef CONFIG_BSD_PROCESS_ACCT
@@ -210,6 +212,10 @@ 0644, NULL, &proc_dol2crvec}, {KERN_PPC_L3CR, "l3cr", NULL, 0, 0644, NULL, &proc_dol3crvec}, +#ifdef CONFIG_DUAL_PLL + {KERN_PPC_PLL, "pll", NULL, 0, + 0644, NULL, &proc_dopllvec}, +#endif #endif {KERN_CTLALTDEL, "ctrl-alt-del", &C_A_D, sizeof(int), 0644, NULL, &proc_dointvec},
Quoted 13 lines · Kevin Diggs
Hi,
I've attached a patch that adds preliminary access to the HID1
register in the 750GX (aka the PLL config register). The patch is against 2.4.30. It has been lightly tested on a PowerMac 8600 with a PowerLogix PowerForce 750GX cpu card.Depending on the values for the
pllx_cfgfield, this should
work on the 750FX as well ... except for the stuff inidle_6xx.S. Since there are plenty of people on this list way more smarterer than me I was hoping someone could answer a question about the powersave modes that some of the PowerPC processors have:
Quoted 7 lines
Since, as I understand it, the clock is shut off to much of the
chip when a powersave mode is engaged does it really buy you that much to switch to a lower clock speed? Wouldn't you be better off shutting off the unused PLL?Also, please note that I am not very experienced creating
patches so please use a backup of your source tree.
Well... I replicated what darwin does here. I don't remember completely but it's possible that there is some kind of CPU errata related to nap and clock speed... or maybe it still makes a difference :)
You want to wakeup fast from nap too, so switching off/on the unused PLL might not be that a good idea. But heh, you are welcome to try & measure.
Ben.