Add get_buf, put_buf api support in spi master.
This can be used in a scenario where spi controller
supports memory mapped operations(typically with flash devices).
So, the memcpy needs top be done in slave devices which need the
required memory mapped address. These api can be used to get that
master address.
These can also be used to turm the master controller clock, as usually
the clocks get turned in spi core. But, in memory mapped case, we will
bypass the spi core and hence needa way out to turn on the controller clock.
Add configure from slave api, which can be used to configure the master
controller with slave specific information.
Add slave info struct, that can be filled with slave properties required by
master controller for its register configuration.
Signed-off-by: Sourav Poddar <sourav.poddar@xxxxxx>
---
v1->v2:
- Added a slave info structure.
- Merge all other header related patches into this.
include/linux/spi/spi.h | 22 ++++++++++++++++++++++
1 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
index 8c62ba7..c91d883 100644
--- a/include/linux/spi/spi.h
+++ b/include/linux/spi/spi.h
@@ -31,6 +31,14 @@
*/
extern struct bus_type spi_bus_type;
+/* For SPI flash */
+struct slave_info {
+ u8 read_opcode;
+ u8 program_opcode;
+ u8 addr_width;
+ u8 dummy_cycles;
+};
+
/**
* struct spi_device - Master side proxy for an SPI slave device
* @dev: Driver model representation of the device.
@@ -73,6 +81,7 @@ extern struct bus_type spi_bus_type;
struct spi_device {
struct device dev;
struct spi_master *master;
+ struct slave_info info; /* flash devices */
u32 max_speed_hz;
u8 chip_select;
u16 mode;
@@ -291,6 +300,14 @@ static inline void spi_unregister_driver(struct spi_driver *sdrv)
* number. Any individual value may be -ENOENT for CS lines that
* are not GPIOs (driven by the SPI controller itself).
*
+ * @get_buf: used for memory mapped cases, when the slave device wants to
+ * 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).
+ * @mmap: Used to show that controller supports memory mapped operation.
* 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
@@ -421,8 +438,13 @@ struct spi_master {
int (*transfer_one)(struct spi_master *master, struct spi_device *spi,
struct spi_transfer *transfer);
+ int __iomem *(*get_buf)(struct spi_master *master);
+ void (*put_buf)(struct spi_master *master);
+ void (*configure_from_slave)(struct spi_device *spi);
+
/* gpio chip select */
int *cs_gpios;
+ bool mmap;
};
static inline void *spi_master_get_devdata(struct spi_master *master)
--
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
