From: Bart Veer <bartv@ecoscentric.com>
To: Peter Niebert <peter@niebert.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] SPI and 9 bit transfers (on AT91)
Date: Thu, 28 May 2009 10:32:00 -0000 [thread overview]
Message-ID: <pn3aapr00c.fsf@delenn.bartv.net> (raw)
In-Reply-To: <06FBFDFF-BA5D-4DDE-967B-49F7725EAEB0@niebert.com> (message from Peter Niebert on Wed, 27 May 2009 19:35:18 +0200)
>>>>> "Peter" == Peter Niebert <peter@niebert.com> writes:
Peter> Just to be sure, this means that the count would be
Peter> "shorts" rather than "bytes" in the case of transfers
Peter> between 9 and 16 bits? I will soon be able to post a
Peter> patched version of the at91_spi driver that allows for
Peter> different bit length transmits.
Peter> Cheers and thanks for eCos, again and again.
The count is the number of data items to be transferred. If the count
is 100 and the SPI device is set up for 9-bit transfers, both tx_data
and rx_data should point at arrays of 100 shorts, i.e. 1600 bits. Only
900 bits would actually get transferred over the SPI bus.
Bart
--
Bart Veer eCos Configuration Architect
eCosCentric Limited The eCos experts http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2009-05-28 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 9:55 Peter Niebert
2009-05-27 16:58 ` Bart Veer
2009-05-27 17:35 ` Peter Niebert
2009-05-28 10:32 ` Bart Veer [this message]
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=pn3aapr00c.fsf@delenn.bartv.net \
--to=bartv@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=peter@niebert.com \
/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).