From: "Jason Hanna" <jason.m.hanna.at.coincident@gmail.com>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>
Cc: spi-devel-general@lists.sourceforge.net,
Stefan Roese <sr@denx.de>,
weo@reccoware.de, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v3] spi: Add PPC4xx SPI driver
Date: Thu, 30 Oct 2008 19:24:43 -0400 [thread overview]
Message-ID: <8f9e78f00810301624k5925a52ah924960f869388233@mail.gmail.com> (raw)
In-Reply-To: <20081029145305.GA3676@yoda.jdub.homelinux.org>
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
next prev parent reply other threads:[~2008-10-30 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 5:48 [PATCH v3] spi: Add PPC4xx SPI driver Stefan Roese
2008-10-29 14:53 ` Josh Boyer
2008-10-30 23:24 ` Jason Hanna [this message]
2008-11-21 3:17 ` [spi-devel-general] " David Brownell
2008-10-31 8:31 ` Stefan Roese
2008-10-31 10:34 ` Josh Boyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f9e78f00810301624k5925a52ah924960f869388233@mail.gmail.com \
--to=jason.m.hanna.at.coincident@gmail.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=sr@denx.de \
--cc=weo@reccoware.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).