@@ -176,6 +176,11 @@ bool spi_mem_generic_supports_op(struct spi_mem *mem,
return false;
}
+ if (!caps->ecc) {
+ if (op->ecc_en)
+ return false;
+ }
+
return spi_mem_check_buswidth(mem, op);
}
EXPORT_SYMBOL_GPL(spi_mem_generic_supports_op);
@@ -94,6 +94,7 @@ enum spi_mem_data_dir {
* operation does not involve transferring data
* @data.buf.in: input buffer (must be DMA-able)
* @data.buf.out: output buffer (must be DMA-able)
+ * @ecc_en: error correction is required
*/
struct spi_mem_op {
struct {
@@ -126,6 +127,8 @@ struct spi_mem_op {
const void *out;
} buf;
} data;
+
+ bool ecc_en;
};
#define SPI_MEM_OP(__cmd, __addr, __dummy, __data) \
@@ -223,9 +226,11 @@ static inline void *spi_mem_get_drvdata(struct spi_mem *mem)
/**
* struct spi_mem_controller_caps - SPI memory controller capabilities
* @dtr: Supports DTR operations
+ * @ecc: Supports operations with error correction
*/
struct spi_mem_controller_caps {
bool dtr;
+ bool ecc;
};
/**
Soon the SPI-NAND core will need a way to request a SPI controller to enable ECC support for a given operation. This is because of the pipelined integration of certain ECC engines, which are directly managed by the SPI controller itself. Introduce a spi_mem_op additional field for this purpose: ecc_en. So far this field is left unset and checked to be false by all the SPI controller drivers in their ->supports_op() hook, as they all call spi_mem_default/dtr_supports_op(). Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> --- drivers/spi/spi-mem.c | 5 +++++ include/linux/spi/spi-mem.h | 5 +++++ 2 files changed, 10 insertions(+)