summaryrefslogtreecommitdiffstats
path: root/drivers/spi/spi-loopback-test.c
diff options
context:
space:
mode:
authorFrieder Schrempf <frieder.schrempf@exceet.de>2018-08-02 14:53:53 +0200
committerMark Brown <broonie@kernel.org>2018-08-02 15:35:41 +0100
commit5d27a9c8ea9e967d00b92a76d4bb242bf7692f2b (patch)
tree81c1eee84492a7b65a991d5069838b86227414c0 /drivers/spi/spi-loopback-test.c
parent06bcb5168d7d49aa3ed449ff13a6d13c30afc3f0 (diff)
downloadblackbird-op-linux-5d27a9c8ea9e967d00b92a76d4bb242bf7692f2b.tar.gz
blackbird-op-linux-5d27a9c8ea9e967d00b92a76d4bb242bf7692f2b.zip
spi: spi-mem: Extend the SPI mem interface to set a custom memory name
When porting (Q)SPI controller drivers from the MTD layer to the SPI layer, the naming scheme for the memory devices changes. To be able to keep compatibility with the old drivers naming scheme, a name field is added to struct spi_mem and a hook is added to let controller drivers set a custom name for the memory device. Example for the FSL QSPI driver: Name with the old driver: 21e0000.qspi, or with multiple devices: 21e0000.qspi-0, 21e0000.qspi-1, ... Name with the new driver without spi_mem_get_name: spi4.0 Suggested-by: Boris Brezillon <boris.brezillon@bootlin.com> Signed-off-by: Frieder Schrempf <frieder.schrempf@exceet.de> Reviewed-by: Boris Brezillon <boris.brezillon@bootlin.com> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/spi/spi-loopback-test.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud