| 13 | |
| 14 | The clock rate can differ between SPI slave devices as only the one with the asserted (active low) chip-select is active. |
| 15 | |
| 16 | The bus is capable of clocking up to 50Mhz althought the MCP2515 can only clock up to 10Mhz. |
| 17 | |
| 18 | The clock rate dictates how long SPI transactions take in real-time, therefore you want to use the highest rate possible to minimize the amount of time a chip is owning the bus. |
| 19 | |
| 20 | The type of activity being performed with each slave device dictates how often and how long each device is owning the bus. |
| 21 | |
| 22 | The SPI subsystem has a SPI message queue which is handled as a FIFO. See the Elixir page linked below for more details. |
| 23 | |
| 24 | Your CPU frequency, co-processors frequency, and kernel tuning will dictate how often the SPI host is serviced in order to service the queue. Questions related to SPI host servicing and queuing should be sent to the linux-spi mailing list !linux-spi@vger.kernel.org |
| 25 | |