[PATCH] ppc32: 8xx pq platform system descriptions

Added ppc_sys device and system definitions for PowerQUICC I devices.

Signed-off-by: Vitaly Bordug <redacted>
-- 
Sincerely,
Vitaly

+/* access ports */
+#define setbits32(_addr, _v) out_be32(&(_addr), in_be32(&(_addr)) |   
(_v))
+#define clrbits32(_addr, _v) out_be32(&(_addr), in_be32(&(_addr)) & ~ 
(_v))
+
+#define setbits16(_addr, _v) out_be16(&(_addr), in_be16(&(_addr)) |   
(_v))
+#define clrbits16(_addr, _v) out_be16(&(_addr), in_be16(&(_addr)) & ~ 
(_v))
+

Needs to go.

+#define MPC8xx_INT_FEC1        SIU_LEVEL1
+#define MPC8xx_INT_FEC2        SIU_LEVEL3
+
+#define MPC8xx_INT_SCC1        (CPM_IRQ_OFFSET + CPMVEC_SCC1)
+#define MPC8xx_INT_SCC2        (CPM_IRQ_OFFSET + CPMVEC_SCC2)
+#define MPC8xx_INT_SCC3        (CPM_IRQ_OFFSET + CPMVEC_SCC3)
+#define MPC8xx_INT_SCC4        (CPM_IRQ_OFFSET + CPMVEC_SCC4)
+#define MPC8xx_INT_SMC1        (CPM_IRQ_OFFSET + CPMVEC_SMC1)
+#define MPC8xx_INT_SMC2        (CPM_IRQ_OFFSET + CPMVEC_SMC2)

Marcelo, we should look at what effect moving CPMVEC_* out of  
commproc.h into irq.h and cleaning things up has on the world.

- kumar

On Aug 19, 2005, at 2:01 PM, Vitaly Bordug wrote:

Added ppc_sys device and system definitions for PowerQUICC I devices.

Signed-off-by: Vitaly Bordug <redacted>
-- 
Sincerely,
Vitaly

<8xx_plats.diff>
<ATT292304.txt>

On Fri, Aug 19, 2005 at 11:01:49PM +0400, Vitaly Bordug wrote:

Added ppc_sys device and system definitions for PowerQUICC I devices.

Signed-off-by: Vitaly Bordug <redacted>
-- 
Sincerely,
Vitaly

Vitaly, Kumar,

Have a few questions:

- Do you have any plans on actually using device model information by
drivers (as was done in the mpc8xxx/gianfar) on m8xx? Its not very clear
to me what are the the practical advantages of that?

- I don't know whether its possible to retrieve 8xx CPUID information
(if there is any). Can't find anything in the manual.

On Aug 21, 2005, at 7:55 PM, Marcelo Tosatti wrote:

- Do you have any plans on actually using device model information by
drivers (as was done in the mpc8xxx/gianfar) on m8xx? Its not very 
clear
to me what are the the practical advantages of that?

It may be nice if we can do that.  We have to be careful about sharing
CPM drivers between the 8xx and CPM2 (82xx/83xx/85xx).  It's tempting,
but I still believe the differences outweigh the similarities.  The 
overhead
of trying to use common drivers would be quite costly on the 8xx.

- I don't know whether its possible to retrieve 8xx CPUID information
(if there is any). Can't find anything in the manual.

We really can't.  The PVR only represents the processor core 
information,
and for the most part they are all the same.  It used to be we could use
the CPM microcode version, but these are now nearly the same.  Some
attempts have been made to probe for CPM peripherals that don't exist,
but it seems on some parts the CPM is the same and the signals just 
aren't
bonded out of the chip.

For the most part, the person doing the kernel configuration just simply
has to know what part they are using.  You have to select the proper
peripherals, and you need the board support for the IO pin routing.
In an embedded environment where resources still need to be
carefully managed, I don't think this is unrealistic.

Thanks.

	-- Dan