From: chris@codeweaver.co.nz
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] ARM7 SPI 9 bit support
Date: Sat, 19 May 2007 09:29:00 -0000 [thread overview]
Message-ID: <64539.203.96.73.230.1179390211.squirrel@codeweaver.co.nz> (raw)
I need to implement 9 bit SPI transfers on an Atmel ARM7 target
(AT91SAM7). At present spi_at91_ only supports 8 bit transfers but the
hardware is good for 8-16. I have had some discussion with my compatriots
but is not yet clear to us if this would be useful outside our immediate
development and hence what would be the preferred implementation. It seems
a new field should be added to at91_spi_dev and used in
spi_at91_transaction, but the fashion in which which to pass data >8 bit
into to the transfer functions is less clear when one considers the many
SPI layers involved which all take char* buffers ???
Any sentiments expressed here will be factored into our decision making
and may influence whether anything useful to the wider community comes
from our developments.
Chris
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2007-05-17 22:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=64539.203.96.73.230.1179390211.squirrel@codeweaver.co.nz \
--to=chris@codeweaver.co.nz \
--cc=ecos-discuss@ecos.sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).