[PATCH] Updated: CPM2 I2C (SDMA and BitBang)

STALE7877d

3 messages, 2 authors, 2005-03-28 · open the first message on its own page

[PATCH] Updated: CPM2 I2C (SDMA and BitBang)

From: Jason McMullan <hidden>
Date: 2005-03-22 21:12:34

Updated (thanks to a quick eye by ebs) patch to add 
CPM2 SDMA and BitBang I2C support to the MPC85xx

This patch gets rid of some really stupid cut & paste errors
during initialization.

-- 
Jason McMullan [off-list ref]
TimeSys Corporation

Re: [PATCH] Updated: CPM2 I2C (SDMA and BitBang)

From: Eugene Surovegin <hidden>
Date: 2005-03-28 04:11:25

On Tue, Mar 22, 2005 at 04:12:30PM -0500, Jason McMullan wrote:
#### Auto-generated patch ####
Date:        Tue, 22 Mar 2005 15:59:01 -0500
Maintainer:  Jason McMullan [off-list ref]
Summary:     CPM/CPM2 I2C driver for Freescale SoC devices
Description: CPM/CPM2 I2C driver for Freescale SoC devices
Depends:
	
###############################

Index of changes:

 drivers/i2c/algos/Kconfig              |    4 
 drivers/i2c/algos/Makefile             |    1 
 drivers/i2c/busses/Kconfig             |   25 +
 drivers/i2c/busses/Makefile            |    1 
 include/linux/i2c-id.h                 |    4 
 linux/drivers/i2c/algos/i2c-algo-cpm.c |  477 +++++++++++++++++++++++++++++++++
 linux/drivers/i2c/busses/i2c-cpm.c     |  219 +++++++++++++++
 linux/include/linux/i2c-algo-cpm.h     |   64 ++++
[snip]

Jason, another thought. Do we really need all this mess with separate 
algo and bus drivers?

Could you make just a bus driver like we have for 4xx, Keywest and 
85xx/52xx/MPC107? It's much cleaner and less confusing IMHO.

--
Eugene

Re: [PATCH] Updated: CPM2 I2C (SDMA and BitBang)

From: Jason McMullan <hidden>
Date: 2005-03-28 14:17:29

On Sun, 2005-03-27 at 20:11 -0800, Eugene Surovegin wrote:
Jason, another thought. Do we really need all this mess with separate 
algo and bus drivers?

Could you make just a bus driver like we have for 4xx, Keywest and 
85xx/52xx/MPC107? It's much cleaner and less confusing IMHO.

I made it separate algo/bus in case you had a PCI-card 85xx design
where:

	a) You booted the card with firmware
	b) The firmware made the card a PCI device with the CPM exposed
	   before you booted the kernel.
        c) The PCI host had to program an EEPROM on the CPM I2C bus
           for configuration to tell it where to get the kernel.

Admittedly, a little far out, but then you could make a
CPM-exposed-by-PCI I2C bus driver.

-- 
Jason McMullan [off-list ref]
TimeSys Corporation
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help