Skip to contentSkip to conversation

SPI bus master driver for the Freescale MPC52xx

DISCUSSION Grant Likely 1 participant 2 messages Sep 23, 2005 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi.

First off, I've included the linuxppc-embedded mailing list in my reply. It's better to mail the list and CC: me rather than just mailing me. There are many others far brighter than me on the list who can provide far more help.

Quoted 1 line · Frank Bennett

Gary:

My name is Grant

Quoted 3 lines

I saw your patch on http://patchwork.ozlabs.org/linuxppc
I'm developing a SPI driver for the Lite5200.

Are you using a PSC or the SPI peripheral? The driver I've written is for = a PSC

Quoted 2 lines

What distribution of Linux is this for?

Any distro you want. It should apply cleanly against any recent 2.6.x kern= el

Quoted 1 line

What is this patch registry all about?

Are you refering to the bit about device drivers registering to the SPI subsystem? If so, the first patch provides the generic SPI infrastructure. Device drivers for SPI masters and SPI slaves register to the SPI subsystem. That way SPI master device drivers are decoupled from SPI slave device drivers. It follows the new device model in the 2.6.x kernels. (See "Linux Device Drivers" book from O'reilly for details.

Quoted 1 line

Can I get a snapshot of the mpc52xx driver stuff?

I've made no changes since posting the patch.

Eventually I'll have a public git tree with all my changes posted in it; but not yet.

Quoted 1 line

How can I contribute to this effort?

Write code, write documentation and post patches. Also, look in the LKML archives. There are two other competing SPI implementations that are being developed. I've been pulled off onto other work so I've not done any additional work. The other code looks more promising.

That being said, my code works for me so it may be usable for you as-is.

cheers,
g.

#2 lore raw

Bah! Your reply-to: address is broken. Check your email client.

let me try that again...

Quoted 7 lines · Grant Likely

Hi.

First off, I've included the linuxppc-embedded mailing list in my reply. It's better to mail the list and CC: me rather than just mailing me. There are many others far brighter than me on the list who can provide far more help.

Quoted 8 lines
Quoted 1 line · Frank Bennett

Gary:

My name is Grant

Quoted 3 lines

I saw your patch on http://patchwork.ozlabs.org/linuxppc
I'm developing a SPI driver for the Lite5200.

Are you using a PSC or the SPI peripheral? The driver I've written is fo=

r a PSC

Quoted 3 lines
Quoted 2 lines

What distribution of Linux is this for?

Any distro you want. It should apply cleanly against any recent 2.6.x ke=

rnel

Quoted 27 lines
Quoted 2 lines

What is this patch registry all about?

Are you refering to the bit about device drivers registering to the SPI subsystem? If so, the first patch provides the generic SPI infrastructure. Device drivers for SPI masters and SPI slaves register to the SPI subsystem. That way SPI master device drivers are decoupled from SPI slave device drivers. It follows the new device model in the 2.6.x kernels. (See "Linux Device Drivers" book from O'reilly for details.

Quoted 1 line

Can I get a snapshot of the mpc52xx driver stuff?

I've made no changes since posting the patch.

Eventually I'll have a public git tree with all my changes posted in it; but not yet.

Quoted 1 line

How can I contribute to this effort?

Write code, write documentation and post patches. Also, look in the LKML archives. There are two other competing SPI implementations that are being developed. I've been pulled off onto other work so I've not done any additional work. The other code looks more promising.

That being said, my code works for me so it may be usable for you as-is.

cheers,
g.