Commit 0c64bc1b authored by John Whitmore's avatar John Whitmore Committed by Mark Brown

spi: Correction to typos in Documentation/spi/spi-summary

Just a few simple typo corrections.
Signed-off-by: default avatarJohn Whitmore <johnfwhitmore@gmail.com>
Signed-off-by: default avatarMark Brown <broonie@linaro.org>
parent 90808738
...@@ -34,7 +34,7 @@ SPI slave functions are usually not interoperable between vendors ...@@ -34,7 +34,7 @@ SPI slave functions are usually not interoperable between vendors
- It may also be used to stream data in either direction (half duplex), - It may also be used to stream data in either direction (half duplex),
or both of them at the same time (full duplex). or both of them at the same time (full duplex).
- Some devices may use eight bit words. Others may different word - Some devices may use eight bit words. Others may use different word
lengths, such as streams of 12-bit or 20-bit digital samples. lengths, such as streams of 12-bit or 20-bit digital samples.
- Words are usually sent with their most significant bit (MSB) first, - Words are usually sent with their most significant bit (MSB) first,
...@@ -121,7 +121,7 @@ active. So the master must set the clock to inactive before selecting ...@@ -121,7 +121,7 @@ active. So the master must set the clock to inactive before selecting
a slave, and the slave can tell the chosen polarity by sampling the a slave, and the slave can tell the chosen polarity by sampling the
clock level when its select line goes active. That's why many devices clock level when its select line goes active. That's why many devices
support for example both modes 0 and 3: they don't care about polarity, support for example both modes 0 and 3: they don't care about polarity,
and alway clock data in/out on rising clock edges. and always clock data in/out on rising clock edges.
How do these driver programming interfaces work? How do these driver programming interfaces work?
...@@ -139,7 +139,7 @@ a command and then reading its response. ...@@ -139,7 +139,7 @@ a command and then reading its response.
There are two types of SPI driver, here called: There are two types of SPI driver, here called:
Controller drivers ... controllers may be built in to System-On-Chip Controller drivers ... controllers may be built into System-On-Chip
processors, and often support both Master and Slave roles. processors, and often support both Master and Slave roles.
These drivers touch hardware registers and may use DMA. These drivers touch hardware registers and may use DMA.
Or they can be PIO bitbangers, needing just GPIO pins. Or they can be PIO bitbangers, needing just GPIO pins.
...@@ -548,7 +548,7 @@ SPI MASTER METHODS ...@@ -548,7 +548,7 @@ SPI MASTER METHODS
DEPRECATED METHODS DEPRECATED METHODS
master->transfer(struct spi_device *spi, struct spi_message *message) master->transfer(struct spi_device *spi, struct spi_message *message)
This must not sleep. Its responsibility is arrange that the This must not sleep. Its responsibility is to arrange that the
transfer happens and its complete() callback is issued. The two transfer happens and its complete() callback is issued. The two
will normally happen later, after other transfers complete, and will normally happen later, after other transfers complete, and
if the controller is idle it will need to be kickstarted. This if the controller is idle it will need to be kickstarted. This
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment