spi: cadence-quadspi: Enable SPI_TX_QUAD
PATCH 1/1 spi: cadence-quadspi: Enable SPI_TX_QUAD
Enable the SPI_TX_QUAD mode bit in the host->mode_bits to support data transmission over four lines to improve the performance.
Tested the functionality on AM62Lx EVM (W25N01JW) in 1S-4S-4S mode.
---
Repo: https://github.com/santhosh21/linux/tree/uL_next
Test results: https://gist.github.com/santhosh21/71ab6646dccc238a0b3c47c0382f219a
Regards,
Santhosh.
drivers/spi/spi-cadence-quadspi.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/spi/spi-cadence-quadspi.c +4 -1
@@ -49,6 +49,7 @@ static_assert(CQSPI_MAX_CHIPSELECT <= SPI_CS_CNT_MAX);/* Capabilities */ #define CQSPI_SUPPORTS_OCTAL BIT(0) +#define CQSPI_SUPPORTS_QUAD BIT(1)#define CQSPI_OP_WIDTH (part) ((part).nbytes ? ilog2((part).buswidth) : 0)
@@ -1888,6 +1889,8 @@ static int cqspi_probe(struct platform_device *pdev) cqspi->master_ref_clk_hz);if (ddata->hwcaps_mask &CQSPI_SUPPORTS_OCTAL ) host->mode_bits |=SPI_RX_OCTAL |SPI_TX_OCTAL ; +if (ddata->hwcaps_mask &CQSPI_SUPPORTS_QUAD ) + host->mode_bits |=SPI_TX_QUAD ;if (!(ddata->quirks &CQSPI_DISABLE_DAC_MODE )) { cqspi->use_direct_mode = true; cqspi->use_direct_mode_wr = true;
@@ -2062,7 +2065,7 @@ static const struct cqspi_driver_platdata k2g_qspi = { };static const struct cqspi_driver_platdata am654_ospi = { - .hwcaps_mask =CQSPI_SUPPORTS_OCTAL , + .hwcaps_mask =CQSPI_SUPPORTS_OCTAL |CQSPI_SUPPORTS_QUAD , .quirks =CQSPI_NEEDS_WR_DELAY , };
Signature · 1 line
2.34.1
Mark Brown
maintainerQuoted 6 lines · Santhosh Kumar K
Enable the
SPI_TX_QUADmode bit in thehost->mode_bitsto support data transmission over four lines to improve the performance.Tested the functionality on AM62Lx EVM (W25N01JW) in 1S-4S-4S mode.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: cadence-quadspi: Enable SPI_TX_QUAD
commit: 1e293574c6f5d5d87acd7d64415eae055d0672e7
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark