82xx CPU features

Kumar Gala galak at kernel.crashing.org
Fri Jan 26 18:24:43 EST 2007


On Jan 25, 2007, at 4:39 PM, Guennadi Liakhovetski wrote:

> Hi all
>
> wandering around the idle code, noticed the following:
>
> #define CPU_FTRS_603	(CPU_FTR_COMMON | CPU_FTR_SPLIT_ID_CACHE | \
> 	    CPU_FTR_MAYBE_CAN_DOZE | CPU_FTR_USE_TB | \
> 	    CPU_FTR_MAYBE_CAN_NAP | CPU_FTR_PPC_LE)
>
> ...
>
> #define CPU_FTRS_82XX	(CPU_FTR_COMMON | CPU_FTR_SPLIT_ID_CACHE | \
> 	    CPU_FTR_MAYBE_CAN_DOZE | CPU_FTR_USE_TB)
>
> Whereas even in
>
> static struct cpu_spec cpu_specs[] = {
> ...
> 	{	/* 82xx (8240, 8245, 8260 are all 603e cores) */
> ...
>
> So, wanted to ask - is there a specific reason why  
> CPU_FTR_MAYBE_CAN_NAP
> is not set for 82xx (as well as CPU_FTR_PPC_LE for that matter...)

For _CAN_NAP, I'm guessing its historic, maybe Dan knows why it  
wasn't set.  What happens if you try to set it?  Are there  
implications at the system level with regards to _CAN_NAP?

I'm looking at the CPU_FTR_PPC_LE it varies if we should use _PPC_LE  
vs _TRUE_LE (or whatever the other one is called).

- k





More information about the Linuxppc-dev mailing list