summaryrefslogtreecommitdiffstats
path: root/drivers/virtio
diff options
context:
space:
mode:
authorGeert Uytterhoeven <geert+renesas@glider.be>2017-05-22 15:11:41 +0200
committerMark Brown <broonie@kernel.org>2017-05-26 13:11:00 +0100
commit6c364062bfed3c34490e85bea52ff6e2d4f0f281 (patch)
tree159d6925ecfac456d6283dff5522c11e40d2ae61 /drivers/virtio
parenta8830cb19cfea04edb0381b52fd90eec44986eb9 (diff)
downloadtalos-obmc-linux-6c364062bfed3c34490e85bea52ff6e2d4f0f281.tar.gz
talos-obmc-linux-6c364062bfed3c34490e85bea52ff6e2d4f0f281.zip
spi: core: Add support for registering SPI slave controllers
Add support for registering SPI slave controllers using the existing SPI master framework: - SPI slave controllers must use spi_alloc_slave() instead of spi_alloc_master(), and should provide an additional callback "slave_abort" to abort an ongoing SPI transfer request, - SPI slave controllers are added to a new "spi_slave" device class, - SPI slave handlers can be bound to the SPI slave device represented by an SPI slave controller using a DT child node named "slave", - Alternatively, (un)binding an SPI slave handler to the SPI slave device represented by an SPI slave controller can be done by (un)registering the slave device through a sysfs virtual file named "slave". From the point of view of an SPI slave protocol handler, an SPI slave controller looks almost like an ordinary SPI master controller. The only exception is that a transfer request will block on the remote SPI master, and may be cancelled using spi_slave_abort(). Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/virtio')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud