From: wzab <wzab@ise.pw.edu.pl>
To: linux-kernel@vger.kernel.org
Subject: Reuse of spi_transfer and spi_message structures for cyclic communication with SPI devices?
Date: Tue, 17 May 2011 22:23:19 +0200 [thread overview]
Message-ID: <4DD2D937.7070803@ise.pw.edu.pl> (raw)
Hi,
I'm writing a device driver for data acquisition system using A/D
converters connected via SPI interface.
To allow flexible ordering of received data, the content
of spi_transfer structures ans spi_message structures
must be set-up in quite sophisticate way before the transfer
may be started.
Refilling of those structures in each sampling cycle will be very
time consuming. I'd prefer to reuse the same structures again and
again, but I can't find any info in the kernel if I'm allowed to.
The documentation suggests to zero spi_transfer ans spi_message
before filling, but doesn't state if they may be used multiple times
with the same I/O buffers without zeroing and refilling.
--
TIA & Regards,
Wojtek Zabolotny
next reply other threads:[~2011-05-17 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 20:23 wzab [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-17 19:21 wzab
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=4DD2D937.7070803@ise.pw.edu.pl \
--to=wzab@ise.pw.edu.pl \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®