Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Use SPI transactions #1

Open
mhaas opened this issue Sep 12, 2015 · 2 comments
Open

Feature Request: Use SPI transactions #1

mhaas opened this issue Sep 12, 2015 · 2 comments

Comments

@mhaas
Copy link

mhaas commented Sep 12, 2015

Using SPI transactions would make the code slightly more robust:
http://dorkbotpdx.org/blog/paul/spi_transactions_in_arduino

Thanks for the library, it's working great here.

@majenkotech
Copy link
Contributor

While SPI transactions would be nice, they aren't widely supported on other platforms (or not officially yet). For instance, I only added SPI transactions to the SPI driver on the chipKIT platform last week, and it's not available in any release version yet.

Personally I much prefer the model of "Request a device from the SPI driver and do all operations on that device" which I use internally. I have a special SPIBus driver from which you request an SPIDevice object which encompasses all the mode, baud, etc settings. You then perform the transfer() operations on the device, not the bus. One day I will get round to releasing it when it's all polished and working nicely.

In due course, when all the primary platforms have SPI Transaction support in their release versions I will be using it more extensively. Until then I need to maintain compatibility.

@mhaas
Copy link
Author

mhaas commented Sep 12, 2015

Thanks for the feedback! I don't really need it, I just figured I would bring it to your attention. But as I can see, you have everything under control there ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants