* [PATCH v4 00/11] mtd/spi-mem: Enable DQS control
@ 2026-11-20 17:14 Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 01/11] spi: spi-mem: Rename the DQS setter and pin field Miquel Raynal
` (11 more replies)
0 siblings, 12 replies; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
For his PHY tuning series on the Cadence QSPI controller embedded in TI
SoCs, Santhosh initially needed to access the availability of the DQS
(data strobe) signal. This is a chip dependent capability, which may
sometimes be enabled.
The SPI memory flag already exist but is too vague for it. Let the SPI
NAND core and SPI NOR core set this flag when relevant (per-chip for SPI
NAND, always for SPI NOR until we can do better). SPI controllers now
feature a DQS capability that they need to fill. Manufacturer drivers
and SPI controllers can now query the usability of the feature to use
it/enable it.
I contributed the spi-mem bit in the previous cycle but my changes were
too simple, and a more complex approach was actually needed. For
applying this series, I would expect all the spi-mem and spi bits to be
taken by Mark, either based on an immutable branch (in which case the
mtd bits can also get in during the same cycle) or directly through b4
(and we will wait for the next cycle to merge the patches). There will
be a temporary regression if we span those patches over two releases:
the PHY tuning will not be optimal because it won't be using the DQS
capability for a period of time. Hence, merging everything in a
single release would be better, but not stricly needed either.
This series applies on top of v7.4-rc2 and Santhosh's PHY tuning series.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
Changes in v4:
- Added a spi-dqs-not-wired DT property to describe boards where the DQS
line is not routed.
- Parsed the property in spi-mem.
- Renamed several helpers to explain what they do more obviously.
- Added a controller DQS capability;
- Expose that DQS is usable only when the memory supports it, the line
is wired and the controller supports it as well.
- Advertised the DQS capability in the Cadence QSPI driver.
- Advertised the DQS capability before the SSDR/ODTR variants are
negotiated.
- Only enabled the Winbond DQS output when spi_mem_dqs_is_usable() reports
it as usable, to avoid useless power consumption.
- Enabled DQS in SPI NOR (always).
- Dropped the already merged spi-mem capability patch from the series.
- Rebased on v7.4-rc2.
- Link to v3: https://lore.kernel.org/r/20260810-winbond-nand-next-phy-tuning-v3-0-a97c3a61e675@bootlin.com
Changes in v3:
- Rebased on top of linux-spi/for-7.3 and dopped all existing
dependencies on the MTD bits.
- Link to v2: https://lore.kernel.org/r/20260807-winbond-nand-next-phy-tuning-v2-0-73595e89d6e3@bootlin.com
Changes in v2:
- Dropped the RFC prefix.
- Rebased on top of v7.2-rc1.
- Dropped the spi patch for now, just allowing to use DQS on a few
Winbond SPI NANDs (can be improved later).
- Link to v1: https://lore.kernel.org/r/20260205-winbond-nand-next-phy-tuning-v1-0-5e7d3976f0f1@bootlin.com
---
Miquel Raynal (11):
spi: spi-mem: Rename the DQS setter and pin field
spi: spi-mem: Clarify the conditions upon which DQS is usable
dt-bindings: spi: Document the spi-dqs-not-wired property
spi: spi-mem: Take the DQS wiring into account
spi: spi-mem: Take the controller DQS support into account
spi: cadence-quadspi: Advertise DQS support
spi: cadence-quadspi: Decouple the read capture bypass from DQS
spi: cadence-quadspi: Check DQS usability before enabling DQS capture
mtd: spi-nor: Advertise DQS support for octal DTR flashes
mtd: spi-nand: Set the DQS spi-mem capability if available
mtd: spi-nand: winbond: Enable the DQS pin on W35N**JW series
.../bindings/spi/spi-peripheral-props.yaml | 10 ++++++++
drivers/mtd/nand/spi/core.c | 3 +++
drivers/mtd/nand/spi/winbond.c | 10 +++++---
drivers/mtd/spi-nor/core.c | 7 ++++++
drivers/spi/spi-cadence-quadspi.c | 11 +++++---
drivers/spi/spi-mem.c | 29 ++++++++++++++--------
include/linux/mtd/spinand.h | 1 +
include/linux/spi/spi-mem.h | 12 ++++++---
8 files changed, 61 insertions(+), 22 deletions(-)
---
base-commit: fd9230005e85472b81c1c7c16afe93dd878996b1
change-id: 20260205-winbond-nand-next-phy-tuning-aabefc018032
prerequisite-message-id: <20261105105832.2134313-1-s-k6@ti.com>
prerequisite-patch-id: 7e80450b6b26ac3240d561a7f9f0e5fe177a89b7
prerequisite-patch-id: 865537f117247ff4312d629514dd06f1f38f1d47
prerequisite-patch-id: 5200192ca3b2cc4a2fdf8afff7ee5c757fdb66b5
prerequisite-patch-id: f41f68176da636e14a8221fde30b3a32cd155bdd
prerequisite-patch-id: d23997b62c52e24d7d92a3f795b2d64ad32a6dc7
prerequisite-patch-id: 7d0c439461665f7c41639343042ddb96937d2838
prerequisite-patch-id: d8770bcd1d4f60e882cdd4ad6f35409a08dc2402
prerequisite-patch-id: 5b96154a5b95e52afc0e3f128212921984713615
prerequisite-patch-id: 500bd167644ed25f95ee48bf7992d79d611b036a
prerequisite-patch-id: 65a2ee2f666180289b3c38aef3e238803ba93f27
prerequisite-patch-id: a58a38e05737feb5f097cafe49f814a4f4a1b252
prerequisite-patch-id: d0717fa96dbc2f99111be023238973932a6c59b4
prerequisite-patch-id: 817e0b94d11c4e7884c962781ff20131a9db1aa9
prerequisite-patch-id: 16ba1c3be3824059d975c0e48a7056b061c2d652
prerequisite-patch-id: f7d67c3465c65f61ec878b6d3f049addd44316af
prerequisite-patch-id: d023f74d37fe6be398aa45a5de3cd70f775cb37a
prerequisite-patch-id: c146c437ba46a28dc74dcebe4c66ff8107ce31a3
prerequisite-patch-id: 14cf3f31d431b4622a4f225939b8d3d3eee21085
prerequisite-patch-id: 95db84235391fa3a39c1947f19411634d762e1f9
Best regards,
--
Miquel Raynal <miquel.raynal@bootlin.com>
^ permalink raw reply [flat|nested] 14+ messages in thread
* [PATCH v4 01/11] spi: spi-mem: Rename the DQS setter and pin field
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
@ 2026-11-20 17:14 ` Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 02/11] spi: spi-mem: Clarify the conditions upon which DQS is usable Miquel Raynal
` (10 subsequent siblings)
11 siblings, 0 replies; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
The current approach was a bit too simple. Using the DQS feature
requires:
1- the chip to feature a DQS pin
2- proper wiring between the host and the chip
3- the controller capability to use it
Rename the helper and the field to reflect that we are talking here
about (1) the chip capability.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/spi/spi-mem.c | 10 +++++-----
include/linux/spi/spi-mem.h | 6 +++---
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/spi/spi-mem.c b/drivers/spi/spi-mem.c
index baf6e430e563..1bea52c6f8a3 100644
--- a/drivers/spi/spi-mem.c
+++ b/drivers/spi/spi-mem.c
@@ -547,7 +547,7 @@ const char *spi_mem_get_name(struct spi_mem *mem)
EXPORT_SYMBOL_GPL(spi_mem_get_name);
/**
- * spi_mem_set_dqs() - Mark DQS as being available
+ * spi_mem_set_dqs_pin_available() - Mark DQS as being available
* @mem: the SPI memory
*
* When reading at high frequencies (> 100MHz), especially when DTR is enabled,
@@ -560,11 +560,11 @@ EXPORT_SYMBOL_GPL(spi_mem_get_name);
* Set the DQS boolean if the feature is available and configured at the chip
* level. Controllers may query this value.
*/
-void spi_mem_set_dqs(struct spi_mem *mem)
+void spi_mem_set_dqs_pin_available(struct spi_mem *mem)
{
- mem->dqs = true;
+ mem->dqs_pin = true;
}
-EXPORT_SYMBOL_GPL(spi_mem_set_dqs);
+EXPORT_SYMBOL_GPL(spi_mem_set_dqs_pin_available);
/**
* spi_mem_has_dqs() - Query whether the DQS is available or not
@@ -574,7 +574,7 @@ EXPORT_SYMBOL_GPL(spi_mem_set_dqs);
*/
bool spi_mem_has_dqs(struct spi_mem *mem)
{
- return mem->dqs;
+ return mem->dqs_pin;
}
EXPORT_SYMBOL_GPL(spi_mem_has_dqs);
diff --git a/include/linux/spi/spi-mem.h b/include/linux/spi/spi-mem.h
index b69f671c40e7..e3c0016be768 100644
--- a/include/linux/spi/spi-mem.h
+++ b/include/linux/spi/spi-mem.h
@@ -275,7 +275,7 @@ struct spi_mem_dirmap_desc {
* @spi: the underlying SPI device
* @drvpriv: spi_mem_driver private data
* @name: name of the SPI memory device
- * @dqs: extra data trobe pin available for high frequency read operations
+ * @dqs_pin: the memory provides a DQS pin
*
* Extra information that describe the SPI memory device and may be needed by
* the controller to properly handle this device should be placed here.
@@ -287,7 +287,7 @@ struct spi_mem {
struct spi_device *spi;
void *drvpriv;
const char *name;
- bool dqs;
+ bool dqs_pin;
};
/**
@@ -474,7 +474,7 @@ bool spi_mem_default_supports_op(struct spi_mem *mem,
}
#endif /* CONFIG_SPI_MEM */
-void spi_mem_set_dqs(struct spi_mem *mem);
+void spi_mem_set_dqs_pin_available(struct spi_mem *mem);
bool spi_mem_has_dqs(struct spi_mem *mem);
int spi_mem_adjust_op_size(struct spi_mem *mem, struct spi_mem_op *op);
void spi_mem_adjust_op_freq(struct spi_mem *mem, struct spi_mem_op *op);
--
2.56.0
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH v4 02/11] spi: spi-mem: Clarify the conditions upon which DQS is usable
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 01/11] spi: spi-mem: Rename the DQS setter and pin field Miquel Raynal
@ 2026-11-20 17:14 ` Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 03/11] dt-bindings: spi: Document the spi-dqs-not-wired property Miquel Raynal
` (9 subsequent siblings)
11 siblings, 0 replies; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
The helper currently only captures the chip capability. Let's rename it
to capture the fact that it is going to reports whether DQS is usable
end-to-end through the upcoming changes.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/spi/spi-mem.c | 12 ++++++------
include/linux/spi/spi-mem.h | 2 +-
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/spi/spi-mem.c b/drivers/spi/spi-mem.c
index 1bea52c6f8a3..8c283953b302 100644
--- a/drivers/spi/spi-mem.c
+++ b/drivers/spi/spi-mem.c
@@ -557,8 +557,7 @@ EXPORT_SYMBOL_GPL(spi_mem_get_name);
* Mitigating this limitation is possible with the addition of a data strobe
* signal, commonly named DQS.
*
- * Set the DQS boolean if the feature is available and configured at the chip
- * level. Controllers may query this value.
+ * Set the DQS pin boolean if the feature is available.
*/
void spi_mem_set_dqs_pin_available(struct spi_mem *mem)
{
@@ -567,16 +566,17 @@ void spi_mem_set_dqs_pin_available(struct spi_mem *mem)
EXPORT_SYMBOL_GPL(spi_mem_set_dqs_pin_available);
/**
- * spi_mem_has_dqs() - Query whether the DQS is available or not
+ * spi_mem_dqs_is_usable() - Query whether the DQS is usable or not
* @mem: the SPI memory
*
- * Return: a boolean indicating whether the DQS signal is available or not.
+ * Return: a boolean indicating whether the DQS signal is usable or not. DQS is
+ * usable when the memory supports it.
*/
-bool spi_mem_has_dqs(struct spi_mem *mem)
+bool spi_mem_dqs_is_usable(struct spi_mem *mem)
{
return mem->dqs_pin;
}
-EXPORT_SYMBOL_GPL(spi_mem_has_dqs);
+EXPORT_SYMBOL_GPL(spi_mem_dqs_is_usable);
/**
* spi_mem_adjust_op_size() - Adjust the data size of a SPI mem operation to
diff --git a/include/linux/spi/spi-mem.h b/include/linux/spi/spi-mem.h
index e3c0016be768..85a61ac62e2c 100644
--- a/include/linux/spi/spi-mem.h
+++ b/include/linux/spi/spi-mem.h
@@ -475,7 +475,7 @@ bool spi_mem_default_supports_op(struct spi_mem *mem,
#endif /* CONFIG_SPI_MEM */
void spi_mem_set_dqs_pin_available(struct spi_mem *mem);
-bool spi_mem_has_dqs(struct spi_mem *mem);
+bool spi_mem_dqs_is_usable(struct spi_mem *mem);
int spi_mem_adjust_op_size(struct spi_mem *mem, struct spi_mem_op *op);
void spi_mem_adjust_op_freq(struct spi_mem *mem, struct spi_mem_op *op);
u64 spi_mem_calc_op_duration(struct spi_mem *mem, struct spi_mem_op *op);
--
2.56.0
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH v4 03/11] dt-bindings: spi: Document the spi-dqs-not-wired property
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 01/11] spi: spi-mem: Rename the DQS setter and pin field Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 02/11] spi: spi-mem: Clarify the conditions upon which DQS is usable Miquel Raynal
@ 2026-11-20 17:14 ` Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 04/11] spi: spi-mem: Take the DQS wiring into account Miquel Raynal
` (8 subsequent siblings)
11 siblings, 0 replies; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
The DQS line is a data strobe line that is typically driven by flash
memories (NOR and NAND) when the data flows from the peripheral to the
host controller when running at high frequencies in order for the data
bits to be sampled by the host at the right moment. The SPI bus already
features a clock but this clock is driven by the host, which means it is
not accounting for any chip internal delay.
Hardware engineers, if they do not expect the frequency to be configured
above the usual limits (dozens of MHz), may not route the DQS line
between the SPI controller and the peripheral.
Describe this possibility with a new optional property so that the DQS
output can be left disabled on designs where this would be
wasteful. Keeping DQS enabled while it is not routed mostly costs
spectral business and extra power consumption. Hence my proposal to keep
"wired" as a safe default.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
.../devicetree/bindings/spi/spi-peripheral-props.yaml | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml b/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml
index d730442e5255..fed6bf5ce72b 100644
--- a/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml
+++ b/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml
@@ -138,6 +138,16 @@ properties:
pattern. Used when the device cannot load the pattern dynamically during
PHY tuning.
+ spi-dqs-not-wired:
+ $ref: /schemas/types.yaml#/definitions/flag
+ description:
+ The DQS (data strobe) line of the peripheral is not routed to the
+ controller. This is only meaningful for peripherals that have a DQS
+ pin, typically octal DDR SPI memories. Not routing this line is a
+ possible board design choice, for example to save a pin when the
+ memory is used at lower frequencies. If this property is absent,
+ the DQS line, if relevant, is assumed to be wired.
+
stacked-memories:
description: Several SPI memories can be wired in stacked mode.
This basically means that either a device features several chip
--
2.56.0
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH v4 04/11] spi: spi-mem: Take the DQS wiring into account
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
` (2 preceding siblings ...)
2026-11-20 17:14 ` [PATCH v4 03/11] dt-bindings: spi: Document the spi-dqs-not-wired property Miquel Raynal
@ 2026-11-20 17:14 ` Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 05/11] spi: spi-mem: Take the controller DQS support " Miquel Raynal
` (7 subsequent siblings)
11 siblings, 0 replies; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
The DQS line may not be routed between the memory and the controller.
Parse the spi-dqs-not-wired property when the SPI memory device is
created and only report DQS as available when the memory supports it and
the line is wired.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/spi/spi-mem.c | 7 +++++--
include/linux/spi/spi-mem.h | 2 ++
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-mem.c b/drivers/spi/spi-mem.c
index 8c283953b302..f2e1ecd49fd6 100644
--- a/drivers/spi/spi-mem.c
+++ b/drivers/spi/spi-mem.c
@@ -8,6 +8,7 @@
#include <linux/dmaengine.h>
#include <linux/iopoll.h>
#include <linux/pm_runtime.h>
+#include <linux/property.h>
#include <linux/spi/spi.h>
#include <linux/spi/spi-mem.h>
#include <linux/sched/task_stack.h>
@@ -570,11 +571,11 @@ EXPORT_SYMBOL_GPL(spi_mem_set_dqs_pin_available);
* @mem: the SPI memory
*
* Return: a boolean indicating whether the DQS signal is usable or not. DQS is
- * usable when the memory supports it.
+ * usable when the memory supports it and the line is wired.
*/
bool spi_mem_dqs_is_usable(struct spi_mem *mem)
{
- return mem->dqs_pin;
+ return mem->dqs_pin && mem->dqs_wired;
}
EXPORT_SYMBOL_GPL(spi_mem_dqs_is_usable);
@@ -1142,6 +1143,8 @@ static int spi_mem_probe(struct spi_device *spi)
return -ENOMEM;
mem->spi = spi;
+ mem->dqs_wired = !device_property_read_bool(&spi->dev,
+ "spi-dqs-not-wired");
if (ctlr->mem_ops && ctlr->mem_ops->get_name)
mem->name = ctlr->mem_ops->get_name(mem);
diff --git a/include/linux/spi/spi-mem.h b/include/linux/spi/spi-mem.h
index 85a61ac62e2c..73fab3b004b5 100644
--- a/include/linux/spi/spi-mem.h
+++ b/include/linux/spi/spi-mem.h
@@ -276,6 +276,7 @@ struct spi_mem_dirmap_desc {
* @drvpriv: spi_mem_driver private data
* @name: name of the SPI memory device
* @dqs_pin: the memory provides a DQS pin
+ * @dqs_wired: the DQS line is routed to the controller
*
* Extra information that describe the SPI memory device and may be needed by
* the controller to properly handle this device should be placed here.
@@ -288,6 +289,7 @@ struct spi_mem {
void *drvpriv;
const char *name;
bool dqs_pin;
+ bool dqs_wired;
};
/**
--
2.56.0
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH v4 05/11] spi: spi-mem: Take the controller DQS support into account
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
` (3 preceding siblings ...)
2026-11-20 17:14 ` [PATCH v4 04/11] spi: spi-mem: Take the DQS wiring into account Miquel Raynal
@ 2026-11-20 17:14 ` Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 06/11] spi: cadence-quadspi: Advertise DQS support Miquel Raynal
` (6 subsequent siblings)
11 siblings, 0 replies; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
Require the controller to advertise DQS support through the new
mem_caps.dqs capability. A controller that cannot use the strobe would
otherwise leave the memory driving a signal that is ignored, which costs
power and EMC pollution.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/spi/spi-mem.c | 8 ++++++--
include/linux/spi/spi-mem.h | 2 ++
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-mem.c b/drivers/spi/spi-mem.c
index f2e1ecd49fd6..c07156e22ccd 100644
--- a/drivers/spi/spi-mem.c
+++ b/drivers/spi/spi-mem.c
@@ -571,11 +571,15 @@ EXPORT_SYMBOL_GPL(spi_mem_set_dqs_pin_available);
* @mem: the SPI memory
*
* Return: a boolean indicating whether the DQS signal is usable or not. DQS is
- * usable when the memory supports it and the line is wired.
+ * usable when the memory supports it, the line is wired and the controller is
+ * capable of using it.
*/
bool spi_mem_dqs_is_usable(struct spi_mem *mem)
{
- return mem->dqs_pin && mem->dqs_wired;
+ struct spi_controller *ctlr = mem->spi->controller;
+
+ return mem->dqs_pin && mem->dqs_wired &&
+ spi_mem_controller_is_capable(ctlr, dqs);
}
EXPORT_SYMBOL_GPL(spi_mem_dqs_is_usable);
diff --git a/include/linux/spi/spi-mem.h b/include/linux/spi/spi-mem.h
index 73fab3b004b5..ad438816eebb 100644
--- a/include/linux/spi/spi-mem.h
+++ b/include/linux/spi/spi-mem.h
@@ -405,6 +405,7 @@ struct spi_controller_mem_ops {
* is a pause in the transfer (eg. internal bus contention or
* DMA arbitration on an interconnect). Features such as NAND
* continuous reads shall not be leveraged.
+ * @dqs: The controller can use the DQS signal provided by the memory
*/
struct spi_controller_mem_caps {
bool dtr;
@@ -413,6 +414,7 @@ struct spi_controller_mem_caps {
bool per_op_freq;
bool secondary_op_tmpl;
bool no_cs_assertion;
+ bool dqs;
};
#define spi_mem_controller_is_capable(ctlr, cap) \
--
2.56.0
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH v4 06/11] spi: cadence-quadspi: Advertise DQS support
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
` (4 preceding siblings ...)
2026-11-20 17:14 ` [PATCH v4 05/11] spi: spi-mem: Take the controller DQS support " Miquel Raynal
@ 2026-11-20 17:14 ` Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 07/11] spi: cadence-quadspi: Decouple the read capture bypass from DQS Miquel Raynal
` (5 subsequent siblings)
11 siblings, 0 replies; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
The Cadence QSPI controller supports DQS read data capture. Advertise this
capability in the controller memory capabilities so that
spi_mem_dqs_is_usable() reports DQS as usable when the memory supports it
and the DQS line is wired.
This lets memory drivers enable the DQS output only when the controller is
able to make use of it.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/spi/spi-cadence-quadspi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/spi/spi-cadence-quadspi.c b/drivers/spi/spi-cadence-quadspi.c
index 2982df7fd092..72a5101c4a8c 100644
--- a/drivers/spi/spi-cadence-quadspi.c
+++ b/drivers/spi/spi-cadence-quadspi.c
@@ -3770,12 +3770,14 @@ static const struct spi_controller_mem_ops cqspi_mem_ops = {
static const struct spi_controller_mem_caps cqspi_mem_caps = {
.dtr = true,
.per_op_freq = true,
+ .dqs = true,
};
static const struct spi_controller_mem_caps cqspi_am654_mem_caps = {
.dtr = true,
.per_op_freq = true,
.no_cs_assertion = true,
+ .dqs = true,
};
static int cqspi_setup_flash(struct cqspi_st *cqspi)
--
2.56.0
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH v4 07/11] spi: cadence-quadspi: Decouple the read capture bypass from DQS
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
` (5 preceding siblings ...)
2026-11-20 17:14 ` [PATCH v4 06/11] spi: cadence-quadspi: Advertise DQS support Miquel Raynal
@ 2026-11-20 17:14 ` Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 08/11] spi: cadence-quadspi: Check DQS usability before enabling DQS capture Miquel Raynal
` (4 subsequent siblings)
11 siblings, 0 replies; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
The READCAPTURE bypass bit is not the logical opposite of the DQS bit.
Bypass selects the legacy delay-based read capture while DQS selects the
data strobe based capture. Both are valid in DTR mode: a DTR read without
a DQS line must use the delay-based capture with bypass disabled.
The tuning helpers currently derive bypass from !use_dqs. This happens to
work while use_dqs is always true in DTR mode, but use_dqs will soon
become false for DTR reads when the DQS line is not usable. Bypass would
then be wrongly enabled during tuning, unlike cqspi_phy_pre_config()
which keeps bypass disabled for DTR.
Store whether the read op is DTR and derive bypass from it instead of
from use_dqs. SDR reads keep bypass enabled and DTR reads keep it
disabled, regardless of the DQS setting.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/spi/spi-cadence-quadspi.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-cadence-quadspi.c b/drivers/spi/spi-cadence-quadspi.c
index 72a5101c4a8c..683924a4a274 100644
--- a/drivers/spi/spi-cadence-quadspi.c
+++ b/drivers/spi/spi-cadence-quadspi.c
@@ -84,6 +84,7 @@ struct cqspi_flash_pdata {
u32 tchsh_ns;
u32 tslch_ns;
bool use_dqs;
+ bool dtr;
bool use_tuned_phy;
bool dll_locked;
u8 cs;
@@ -1149,7 +1150,7 @@ static int cqspi_tune_phy_read(struct cqspi_flash_pdata *f_pdata, bool enable)
if (ret)
return ret;
- cqspi_readdata_capture(cqspi, !f_pdata->use_dqs, f_pdata->use_dqs,
+ cqspi_readdata_capture(cqspi, !f_pdata->dtr, f_pdata->use_dqs,
f_pdata->phy_setting.read_delay);
reg = readl(reg_base + CQSPI_REG_CONFIG);
@@ -2137,7 +2138,7 @@ static int cqspi_phy_apply_setting(struct cqspi_flash_pdata *f_pdata,
f_pdata->phy_setting.tx = phy->tx;
f_pdata->phy_setting.read_delay = phy->read_delay;
- cqspi_readdata_capture(cqspi, !f_pdata->use_dqs, f_pdata->use_dqs,
+ cqspi_readdata_capture(cqspi, !f_pdata->dtr, f_pdata->use_dqs,
phy->read_delay);
return 0;
@@ -3534,6 +3535,8 @@ static int cqspi_am654_ospi_execute_tuning(struct spi_mem *mem,
f_pdata->phy_read_op.max_freq = mem->spi->post_config_max_speed_hz;
+ f_pdata->dtr = op_is_dtr;
+
if (op_is_dtr) {
f_pdata->use_dqs = true;
cqspi_phy_pre_config(cqspi, f_pdata, false);
--
2.56.0
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH v4 08/11] spi: cadence-quadspi: Check DQS usability before enabling DQS capture
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
` (6 preceding siblings ...)
2026-11-20 17:14 ` [PATCH v4 07/11] spi: cadence-quadspi: Decouple the read capture bypass from DQS Miquel Raynal
@ 2026-11-20 17:14 ` Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 09/11] mtd: spi-nor: Advertise DQS support for octal DTR flashes Miquel Raynal
` (3 subsequent siblings)
11 siblings, 0 replies; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
The DTR tuning path unconditionally enables DQS capture. But DQS is only
usable when the memory supports it, the DQS line is wired to the
controller and the controller is capable. Use the spi-mem helper that
combines these conditions instead of assuming DQS is always available.
This lets the driver fall back to delay-based capture for DTR memories
that do not have a usable DQS line.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/spi/spi-cadence-quadspi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi-cadence-quadspi.c b/drivers/spi/spi-cadence-quadspi.c
index 683924a4a274..05f64ebb1965 100644
--- a/drivers/spi/spi-cadence-quadspi.c
+++ b/drivers/spi/spi-cadence-quadspi.c
@@ -3538,7 +3538,7 @@ static int cqspi_am654_ospi_execute_tuning(struct spi_mem *mem,
f_pdata->dtr = op_is_dtr;
if (op_is_dtr) {
- f_pdata->use_dqs = true;
+ f_pdata->use_dqs = spi_mem_dqs_is_usable(mem);
cqspi_phy_pre_config(cqspi, f_pdata, false);
ret = cqspi_phy_tuning_ddr(f_pdata, mem);
} else {
--
2.56.0
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH v4 09/11] mtd: spi-nor: Advertise DQS support for octal DTR flashes
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
` (7 preceding siblings ...)
2026-11-20 17:14 ` [PATCH v4 08/11] spi: cadence-quadspi: Check DQS usability before enabling DQS capture Miquel Raynal
@ 2026-11-20 17:14 ` Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 10/11] mtd: spi-nand: Set the DQS spi-mem capability if available Miquel Raynal
` (2 subsequent siblings)
11 siblings, 0 replies; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
The SPI NOR core does not advertise the DQS capability to the controller,
so spi_mem_dqs_is_usable() returns false for SPI NOR flashes even when
they support DQS. Controllers able to use DQS read data capture are
therefore not able to enable it with octal DTR flashes.
Advertise the DQS pin when the read protocol is octal DTR. DQS support is
a per-flash capability which should be described in the flash_info tables,
but there is no flag for it yet. Keep a TODO in the code and enable the
feature by default for all octal DTR flashes until the per-flash
description is added.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/mtd/spi-nor/core.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/mtd/spi-nor/core.c b/drivers/mtd/spi-nor/core.c
index ecf5fdf38471..b78c8fb5a101 100644
--- a/drivers/mtd/spi-nor/core.c
+++ b/drivers/mtd/spi-nor/core.c
@@ -3638,6 +3638,13 @@ static int spi_nor_probe(struct spi_mem *spimem)
return -ENOMEM;
}
+ /*
+ * TODO: DQS support is a per-flash capability which should be described
+ * in the flash_info tables, it is considered enabled by default.
+ */
+ if (nor->read_proto == SNOR_PROTO_8_8_8_DTR)
+ spi_mem_set_dqs_pin_available(spimem);
+
/*
* Populate the persistent template and run PHY tuning before dirmap
* creation so the validated frequency feeds into the dirmap op.
--
2.56.0
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH v4 10/11] mtd: spi-nand: Set the DQS spi-mem capability if available
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
` (8 preceding siblings ...)
2026-11-20 17:14 ` [PATCH v4 09/11] mtd: spi-nor: Advertise DQS support for octal DTR flashes Miquel Raynal
@ 2026-11-20 17:14 ` Miquel Raynal
2026-11-20 17:30 ` sashiko-bot
2026-11-20 17:14 ` [PATCH v4 11/11] mtd: spi-nand: winbond: Enable the DQS pin on W35N**JW series Miquel Raynal
2026-11-20 17:51 ` [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Mark Brown
11 siblings, 1 reply; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
Check whether the NAND is capable of generating a DQS signal and advertise
the capability through the spi-mem layer. Do it as soon as the chip is
identified and before the SSDR/ODTR operation variants are negotiated, so
that controllers can take the capability into account when they need it.
Whether the DQS line is actually wired is described by the
spi-dqs-not-wired DT property and handled by the spi-mem layer, which
only reports DQS as available when the chip supports it, the line is
wired and the controller can use it.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/mtd/nand/spi/core.c | 3 +++
include/linux/mtd/spinand.h | 1 +
2 files changed, 4 insertions(+)
diff --git a/drivers/mtd/nand/spi/core.c b/drivers/mtd/nand/spi/core.c
index fee4a48b4c7f..6e1b7976d237 100644
--- a/drivers/mtd/nand/spi/core.c
+++ b/drivers/mtd/nand/spi/core.c
@@ -1797,6 +1797,9 @@ int spinand_match_and_init(struct spinand_device *spinand,
}
}
+ if (spinand->flags & SPINAND_HAS_DQS)
+ spi_mem_set_dqs_pin_available(spinand->spimem);
+
/* I/O variants selection with octo-spi DDR commands (optional) */
ret = spinand_init_odtr_instruction_set(spinand);
diff --git a/include/linux/mtd/spinand.h b/include/linux/mtd/spinand.h
index 87107f0955eb..990d3e9ac3fe 100644
--- a/include/linux/mtd/spinand.h
+++ b/include/linux/mtd/spinand.h
@@ -492,6 +492,7 @@ struct spinand_ecc_info {
#define SPINAND_HAS_READ_PLANE_SELECT_BIT BIT(3)
#define SPINAND_NO_RAW_ACCESS BIT(4)
#define SPINAND_ODTR_PACKED_PAGE_READ BIT(5)
+#define SPINAND_HAS_DQS BIT(6)
/**
* struct spinand_ondie_ecc_conf - private SPI-NAND on-die ECC engine structure
--
2.56.0
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH v4 11/11] mtd: spi-nand: winbond: Enable the DQS pin on W35N**JW series
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
` (9 preceding siblings ...)
2026-11-20 17:14 ` [PATCH v4 10/11] mtd: spi-nand: Set the DQS spi-mem capability if available Miquel Raynal
@ 2026-11-20 17:14 ` Miquel Raynal
2026-11-20 17:51 ` [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Mark Brown
11 siblings, 0 replies; 14+ messages in thread
From: Miquel Raynal @ 2026-11-20 17:14 UTC (permalink / raw)
To: Mark Brown, Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-spi, linux-kernel, linux-mtd, devicetree, Miquel Raynal
These chips have a DQS pin. Enable its output in DTR mode when the line is
reported as available by the spi-mem layer, which means the chip has DQS,
the line is wired to the controller and the controller supports DQS. There
is apparently no issue in setting it for lower frequencies, and the extra
power consumption seems very low compared to the current drawn by the NAND
array itself while operating, but keep it disabled when the line is not
wired or the controller cannot use it to avoid useless power consumption.
This setting will be required for high speed I/O transfers (with PHY
tuning).
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/mtd/nand/spi/winbond.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/mtd/nand/spi/winbond.c b/drivers/mtd/nand/spi/winbond.c
index 810975808c97..336bf743778c 100644
--- a/drivers/mtd/nand/spi/winbond.c
+++ b/drivers/mtd/nand/spi/winbond.c
@@ -667,7 +667,9 @@ static int w35n0xjw_vcr_cfg(struct spinand_device *spinand,
else if (!single && !dtr)
io_mode = W35N01JW_VCR_IO_MODE_OCTAL_SDR;
else if (!single && dtr)
- io_mode = W35N01JW_VCR_IO_MODE_OCTAL_DDR;
+ io_mode = spi_mem_dqs_is_usable(spinand->spimem) ?
+ W35N01JW_VCR_IO_MODE_OCTAL_DDR_DS :
+ W35N01JW_VCR_IO_MODE_OCTAL_DDR;
else
return -EINVAL;
@@ -749,7 +751,7 @@ static const struct spinand_info winbond_spinand_table[] = {
&write_cache_octal_variants,
&update_cache_octal_variants,
&cont_read_cache_octal_variants),
- 0,
+ SPINAND_HAS_DQS,
SPINAND_INFO_VENDOR_OPS(&winbond_w35_ops),
SPINAND_ECCINFO(&w35n01jw_ooblayout, w25w35nxxjw_ecc_get_status),
SPINAND_CONFIGURE_CHIP(w35n0xjw_vcr_cfg),
@@ -804,7 +806,7 @@ static const struct spinand_info winbond_spinand_table[] = {
&write_cache_octal_variants,
&update_cache_octal_variants,
&cont_read_cache_octal_variants),
- SPINAND_ODTR_PACKED_PAGE_READ,
+ SPINAND_ODTR_PACKED_PAGE_READ | SPINAND_HAS_DQS,
SPINAND_INFO_VENDOR_OPS(&winbond_w35_ops),
SPINAND_ECCINFO(&w35n01jw_ooblayout, w25w35nxxjw_ecc_get_status),
SPINAND_CONFIGURE_CHIP(w35n0xjw_vcr_cfg),
@@ -845,7 +847,7 @@ static const struct spinand_info winbond_spinand_table[] = {
&write_cache_octal_variants,
&update_cache_octal_variants,
&cont_read_cache_octal_variants),
- SPINAND_ODTR_PACKED_PAGE_READ,
+ SPINAND_ODTR_PACKED_PAGE_READ | SPINAND_HAS_DQS,
SPINAND_INFO_VENDOR_OPS(&winbond_w35_ops),
SPINAND_ECCINFO(&w35n01jw_ooblayout, w25w35nxxjw_ecc_get_status),
SPINAND_CONFIGURE_CHIP(w35n0xjw_vcr_cfg),
--
2.56.0
^ permalink raw reply related [flat|nested] 14+ messages in thread
* Re: [PATCH v4 10/11] mtd: spi-nand: Set the DQS spi-mem capability if available
2026-11-20 17:14 ` [PATCH v4 10/11] mtd: spi-nand: Set the DQS spi-mem capability if available Miquel Raynal
@ 2026-11-20 17:30 ` sashiko-bot
0 siblings, 0 replies; 14+ messages in thread
From: sashiko-bot @ 2026-11-20 17:30 UTC (permalink / raw)
To: Miquel Raynal, Mark Brown, Richard Weinberger,
Vignesh Raghavendra, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, Pratyush Yadav, Michael Walle, Takahiro Kuwano
Cc: Thomas Petazzoni, praneeth, u-kumar1, p-mantena, a-dutta, s-k6,
linux-mtd, devicetree
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] mtd: spinand: spi_mem_set_dqs_pin_available() called after
SSDR negotiation
--
commit ded1f01b00a338383ed4e62228f6b415856c9df3
Author: Miquel Raynal <miquel.raynal@bootlin.com>
mtd: spi-nand: Set the DQS spi-mem capability if available
This commit adds the SPINAND_HAS_DQS flag and calls
spi_mem_set_dqs_pin_available() in spinand_match_and_init() when a
matched SPI-NAND chip supports DQS.
> diff --git a/drivers/mtd/nand/spi/core.c b/drivers/mtd/nand/spi/core.c
> index fee4a48b4c7f3..6e1b7976d2379 100644
> --- a/drivers/mtd/nand/spi/core.c
> +++ b/drivers/mtd/nand/spi/core.c
> @@ -1797,6 +1797,9 @@ int spinand_match_and_init(struct spinand_device *spinand,
> }
> }
>
> + if (spinand->flags & SPINAND_HAS_DQS)
> + spi_mem_set_dqs_pin_available(spinand->spimem);
> +
> /* I/O variants selection with octo-spi DDR commands (optional) */
>
> ret = spinand_init_odtr_instruction_set(spinand);
[Severity: Medium]
Should spi_mem_set_dqs_pin_available() be called right after
spinand->flags is initialized, before SSDR operation variants are
selected?
Placing it here leaves spinand->spimem->dqs_pin false while
spinand_select_op_variant(spinand, SSDR, ...) and
spinand_support_vendor_ops(spinand, info, SSDR) run, which also evaluate
1S-command DTR read variants such as
SPINAND_PAGE_READ_FROM_CACHE_1S_1D_8D_OP.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261120-winbond-nand-next-phy-tuning-v4-0-8c21e1f71f41@bootlin.com?part=10
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH v4 00/11] mtd/spi-mem: Enable DQS control
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
` (10 preceding siblings ...)
2026-11-20 17:14 ` [PATCH v4 11/11] mtd: spi-nand: winbond: Enable the DQS pin on W35N**JW series Miquel Raynal
@ 2026-11-20 17:51 ` Mark Brown
11 siblings, 0 replies; 14+ messages in thread
From: Mark Brown @ 2026-11-20 17:51 UTC (permalink / raw)
To: Miquel Raynal
Cc: Richard Weinberger, Vignesh Raghavendra, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Pratyush Yadav, Michael Walle,
Takahiro Kuwano, Thomas Petazzoni, praneeth, u-kumar1, p-mantena,
a-dutta, s-k6, linux-spi, linux-kernel, linux-mtd, devicetree
[-- Attachment #1: Type: text/plain, Size: 251 bytes --]
On Fri, Nov 20, 2026 at 06:14:26PM +0100, Miquel Raynal wrote:
> This series applies on top of v7.4-rc2 and Santhosh's PHY tuning series.
Please don't send patches that depend on other in flight serieses, it
just makes things much harder to manage.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2026-11-20 17:51 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-20 17:14 [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 01/11] spi: spi-mem: Rename the DQS setter and pin field Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 02/11] spi: spi-mem: Clarify the conditions upon which DQS is usable Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 03/11] dt-bindings: spi: Document the spi-dqs-not-wired property Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 04/11] spi: spi-mem: Take the DQS wiring into account Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 05/11] spi: spi-mem: Take the controller DQS support " Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 06/11] spi: cadence-quadspi: Advertise DQS support Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 07/11] spi: cadence-quadspi: Decouple the read capture bypass from DQS Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 08/11] spi: cadence-quadspi: Check DQS usability before enabling DQS capture Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 09/11] mtd: spi-nor: Advertise DQS support for octal DTR flashes Miquel Raynal
2026-11-20 17:14 ` [PATCH v4 10/11] mtd: spi-nand: Set the DQS spi-mem capability if available Miquel Raynal
2026-11-20 17:30 ` sashiko-bot
2026-11-20 17:14 ` [PATCH v4 11/11] mtd: spi-nand: winbond: Enable the DQS pin on W35N**JW series Miquel Raynal
2026-11-20 17:51 ` [PATCH v4 00/11] mtd/spi-mem: Enable DQS control Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox