Skip to content

Give examples of bus wrappers #668

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Give examples of bus wrappers #668

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion embedded-hal-bus/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,9 @@ while `SpiDevice` represents a device on that bus. For further details on these
However, device drivers should use the `SpiDevice` traits, _not the `SpiBus` traits_ if at all possible
in order to allow for sharing of the bus they are connected to.

This crate provides mechanisms to connect a `SpiBus` and a `SpiDevice`.
This crate provides mechanisms to connect a `SpiBus` and a `SpiDevice`. See for instance `ExclusiveDevice::new_no_delay`
or `ExclusiveDevice::new`, or similarly for `CriticalSectionDevice`, `AtomicDevice`, `RefCellDevice`, etc., which wrap an
`SpiBus` and provide an `SpiDevice` with differing access semantics.

## I2C

Expand Down