There are few use cases encountered where the master controller
depends on the slave parameters for some of its register
configure. Add an api in spi master which can be used to enable the
above feature.
Typical usecase encountered till now is
- ti qspi controller required flash opcodes to configure its set up
register for memory mapped operations.
There was another discussion on some LUT registers for some other
qspi controller in mailing list, these feature can also be used for
that case also.
Signed-off-by: Sourav Poddar <sourav.poddar@xxxxxx>
---
include/linux/spi/spi.h | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
index 3b3743d..4be969a 100644
--- a/include/linux/spi/spi.h
+++ b/include/linux/spi/spi.h
@@ -295,6 +295,9 @@ static inline void spi_unregister_driver(struct spi_driver *sdrv)
* know the address to be used for memcopy.
* @put_buf: Used for memory mapped cases after get_buf, after the memcpy
* has finished.
+ * @configure_from_slave: Used when SPI controller has registers which need
+ * to be configured from slave specifics information(typical use case for
+ * SPI flash device).
* Each SPI master controller can communicate with one or more @spi_device
* children. These make a small bus, sharing MOSI, MISO and SCK signals
* but not chip select signals. Each device may be configured to use a
@@ -427,6 +430,7 @@ struct spi_master {
void (*get_buf)(struct spi_master *master);
void (*put_buf)(struct spi_master *master);
+ void (*configure_from_slave)(struct spi_device *spi, u8 *val);
/* gpio chip select */
int *cs_gpios;
--
1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
