Patchwork housekeeping for: spi-devel-general
| Newsgroups | org.kernel.vger.linux-spi |
|---|---|
| Message-ID | <178431469526.1834672.1911710487038586514.git-patchwork-housekeeping@kernel.org> |
Latest series: [v5] spi: cadence-quadspi: add PHY tuning support (2026-07-17T18:50:59)
Superseding: [v4] spi: cadence-quadspi: add PHY tuning support (2026-06-18T07:37:09):
[v4,01/16] spi: dt-bindings: add spi-max-post-config-frequency property
[v4,02/16] spi: dt-bindings: add spi-phy-pattern-partition property
[v4,03/16] spi: parse spi-max-post-config-frequency into post_config_max_speed_hz
[v4,04/16] spi: spi-mem: teach spi_mem_adjust_op_freq() about post-config ops
[v4,05/16] spi: spi-mem: add execute_tuning callback and spi_mem_execute_tuning()
[v4,06/16] spi: cadence-quadspi: move cqspi_readdata_capture earlier
[v4,07/16] spi: cadence-quadspi: add DQS support to read data capture
[v4,08/16] spi: cadence-quadspi: add PHY tuning support
[v4,09/16] spi: cadence-quadspi: skip DDR PHY tuning for 2-byte-address ops (i2383)
[v4,10/16] spi: cadence-quadspi: refactor direct read path for PHY support
[v4,11/16] spi: cadence-quadspi: enable PHY for direct reads
[v4,12/16] spi: cadence-quadspi: enable PHY for indirect writes
[v4,13/16] mtd: spinand: extract variant ranking logic into spinand_op_find_best()
[v4,14/16] mtd: spinand: negotiate optimal PHY operating point before dirmap creation
[v4,15/16] mtd: spi-nor: extract read op template construction into helper
[v4,16/16] mtd: spi-nor: run PHY tuning after init and update dirmap frequency
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html