linux-kernel - Reuse of spi_transfer and spi_message structures for cyclic communication with SPI devices?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4DD2D937.7070803@ise.pw.edu.pl>
Date:	Tue, 17 May 2011 22:23:19 +0200
From:	wzab <wzab@....pw.edu.pl>
To:	linux-kernel@...r.kernel.org
Subject: Reuse of spi_transfer and spi_message structures for cyclic communication
 with SPI devices?

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/