On Wed, Oct 29, 2008 at 10:53 AM, Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
> Also, do you have a patch for a DTS file that gives an example of how to> instantiate the SPI stuff in the device tree?
I'll second that request. I've updated the device tree for my Kilauea
(405EX) board but am not sure I have everything correct.
Also, any pointers to sample/test code incorporating a spi protocol
driver would be incredibly helpful. I'm very new to device driver
programming and don't really know what I'm doing yet. I seem to be
getting the spi_ppc4xx and spi_bitbang modules loaded, but am unsure
how to verify proper initialization and what next steps I need to
follow in order to develop and associate a protocol driver.
I'd like to start quite simply - some test routines that would drive
data over the SPI connector on my Kilauea, using a spare GPIO pin as a
chip select. I've got a logic analyzer from which to verify the
results.
I've been reading through all the documentation I can find but am a
little stuck. A concrete example with a SPI protocol driver would be
quite useful.
Thanks,
-jmh

On Thursday 30 October 2008, Jason Hanna wrote:
> Also, any pointers to sample/test code incorporating a spi protocol> driver would be incredibly helpful.
Look at Documentation/spi/*.c ... for user mode code
hooking up through "spidev".
> I'm very new to device driver > programming and don't really know what I'm doing yet. I seem to be> getting the spi_ppc4xx and spi_bitbang modules loaded, but am unsure> how to verify proper initialization and what next steps I need to> follow in order to develop and associate a protocol driver.
Documentation/spi/spi-summary should help.
And sticking a 'scope on the outputs (as you
said you plan) is a decent place to start,
if you don't have something to talk to yet.
- dave