All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Santhosh Kumar K <s-k6@ti.com>
Cc: <broonie@kernel.org>,  <robh@kernel.org>,  <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>,  <richard@nod.at>,  <vigneshr@ti.com>,
	<tudor.ambarus@linaro.org>,  <pratyush@kernel.org>,
	 <mwalle@kernel.org>, <linux-spi@vger.kernel.org>,
	 <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	 <linux-mtd@lists.infradead.org>, <praneeth@ti.com>,
	 <u-kumar1@ti.com>,  <p-mantena@ti.com>, <a-dutta@ti.com>
Subject: Re: [RFC PATCH v2 08/12] spi: cadence-quadspi: read 'has-dqs' DT property
Date: Thu, 05 Feb 2026 18:35:51 +0100	[thread overview]
Message-ID: <87h5rvgkjs.fsf@bootlin.com> (raw)
In-Reply-To: <20260113141617.1905039-9-s-k6@ti.com> (Santhosh Kumar K.'s message of "Tue, 13 Jan 2026 19:46:13 +0530")

On 13/01/2026 at 19:46:13 +0530, Santhosh Kumar K <s-k6@ti.com> wrote:

> Add a boolean field to struct cqspi_flash_pdata to store whether the
> attached flash device supports DQS (Data Strobe) mode. Read this from
> the 'spi-has-dqs' device tree property during flash node parsing.
>
> This is preparatory infrastructure for PHY tuning support. The field
> will be used by subsequent patches to configure read data capture timing
> with DQS enabled for improved margins in high-speed operations.
>
> Signed-off-by: Santhosh Kumar K <s-k6@ti.com>

As mentioned in my answer to the cover letter, I am not too much in
favour of this property because this is something that is somewhat
related to the chip ID, thus discoverable. I drafted something to get
rid of this property already, I will share it for opening the
discussion.

However, for now I am closing my eyes on the fact that the DQS pin might
not be wired to the controller. In this case we will need some kind of
"dqs-not-wired" DT property, that's true, but also easily manageable at
the core level later, when/if the need arises.

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Santhosh Kumar K <s-k6@ti.com>
Cc: <broonie@kernel.org>,  <robh@kernel.org>,  <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>,  <richard@nod.at>,  <vigneshr@ti.com>,
	<tudor.ambarus@linaro.org>,  <pratyush@kernel.org>,
	 <mwalle@kernel.org>, <linux-spi@vger.kernel.org>,
	 <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	 <linux-mtd@lists.infradead.org>, <praneeth@ti.com>,
	 <u-kumar1@ti.com>,  <p-mantena@ti.com>, <a-dutta@ti.com>
Subject: Re: [RFC PATCH v2 08/12] spi: cadence-quadspi: read 'has-dqs' DT property
Date: Thu, 05 Feb 2026 18:35:51 +0100	[thread overview]
Message-ID: <87h5rvgkjs.fsf@bootlin.com> (raw)
In-Reply-To: <20260113141617.1905039-9-s-k6@ti.com> (Santhosh Kumar K.'s message of "Tue, 13 Jan 2026 19:46:13 +0530")

On 13/01/2026 at 19:46:13 +0530, Santhosh Kumar K <s-k6@ti.com> wrote:

> Add a boolean field to struct cqspi_flash_pdata to store whether the
> attached flash device supports DQS (Data Strobe) mode. Read this from
> the 'spi-has-dqs' device tree property during flash node parsing.
>
> This is preparatory infrastructure for PHY tuning support. The field
> will be used by subsequent patches to configure read data capture timing
> with DQS enabled for improved margins in high-speed operations.
>
> Signed-off-by: Santhosh Kumar K <s-k6@ti.com>

As mentioned in my answer to the cover letter, I am not too much in
favour of this property because this is something that is somewhat
related to the chip ID, thus discoverable. I drafted something to get
rid of this property already, I will share it for opening the
discussion.

However, for now I am closing my eyes on the fact that the DQS pin might
not be wired to the controller. In this case we will need some kind of
"dqs-not-wired" DT property, that's true, but also easily manageable at
the core level later, when/if the need arises.

Thanks,
Miquèl

  reply	other threads:[~2026-02-05 17:36 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13 14:16 [RFC PATCH v2 00/12] spi: cadence-quadspi: add PHY tuning support Santhosh Kumar K
2026-01-13 14:16 ` Santhosh Kumar K
2026-01-13 14:16 ` [RFC PATCH v2 01/12] spi: dt-bindings: add spi-has-dqs property Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-02-04 10:46   ` Miquel Raynal
2026-02-04 10:46     ` Miquel Raynal
2026-02-05 17:46     ` Santhosh Kumar K
2026-02-05 17:46       ` Santhosh Kumar K
2026-02-05 18:06       ` Miquel Raynal
2026-02-05 18:06         ` Miquel Raynal
2026-01-13 14:16 ` [RFC PATCH v2 02/12] spi: spi-mem: add controller tuning support Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-01-13 14:16 ` [RFC PATCH v2 03/12] mtd: spinand: perform controller tuning during probe Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-02-05 17:35   ` Miquel Raynal
2026-02-05 17:35     ` Miquel Raynal
2026-02-06 19:23     ` Santhosh Kumar K
2026-02-06 19:23       ` Santhosh Kumar K
2026-01-13 14:16 ` [RFC PATCH v2 04/12] mtd: spi-nor: extract read operation setup into helper Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-01-13 14:16 ` [RFC PATCH v2 05/12] mtd: spi-nor: perform controller tuning during probe Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-01-13 14:16 ` [RFC PATCH v2 06/12] spi: cadence-quadspi: move cqspi_readdata_capture earlier Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-02-05 17:35   ` Miquel Raynal
2026-02-05 17:35     ` Miquel Raynal
2026-01-13 14:16 ` [RFC PATCH v2 07/12] spi: cadence-quadspi: add DQS support to read data capture Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-02-05 17:35   ` Miquel Raynal
2026-02-05 17:35     ` Miquel Raynal
2026-01-13 14:16 ` [RFC PATCH v2 08/12] spi: cadence-quadspi: read 'has-dqs' DT property Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-02-05 17:35   ` Miquel Raynal [this message]
2026-02-05 17:35     ` Miquel Raynal
2026-02-19 12:14     ` Michael Walle
2026-02-19 12:14       ` Michael Walle
2026-02-20  8:21       ` Miquel Raynal
2026-02-20  8:21         ` Miquel Raynal
2026-01-13 14:16 ` [RFC PATCH v2 09/12] spi: cadence-quadspi: add PHY tuning infrastructure Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-02-05 17:39   ` Miquel Raynal
2026-02-05 17:39     ` Miquel Raynal
2026-02-06 19:25     ` Santhosh Kumar K
2026-02-06 19:25       ` Santhosh Kumar K
2026-02-13  8:18       ` Miquel Raynal
2026-02-13  8:18         ` Miquel Raynal
2026-02-18 18:07         ` Santhosh Kumar K
2026-02-18 18:07           ` Santhosh Kumar K
2026-02-19 10:30           ` Miquel Raynal
2026-02-19 10:30             ` Miquel Raynal
2026-02-09  9:48   ` Michael Walle
2026-02-09  9:48     ` Michael Walle
2026-02-12 10:50     ` Miquel Raynal
2026-02-12 10:50       ` Miquel Raynal
2026-02-12 11:14       ` Michael Walle
2026-02-12 11:14         ` Michael Walle
2026-02-12 12:55         ` Miquel Raynal
2026-02-12 12:55           ` Miquel Raynal
2026-02-18 18:07           ` Santhosh Kumar K
2026-02-18 18:07             ` Santhosh Kumar K
2026-02-19  8:33             ` Michael Walle
2026-02-19  8:33               ` Michael Walle
2026-02-19 10:34             ` Miquel Raynal
2026-02-19 10:34               ` Miquel Raynal
2026-01-13 14:16 ` [RFC PATCH v2 10/12] spi: cadence-quadspi: implement PHY tuning algorithm Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-02-05 17:42   ` Miquel Raynal
2026-02-05 17:42     ` Miquel Raynal
2026-01-13 14:16 ` [RFC PATCH v2 11/12] spi: cadence-quadspi: restrict PHY frequency to tuned operations Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-02-05 17:47   ` Miquel Raynal
2026-02-05 17:47     ` Miquel Raynal
2026-02-06 19:27     ` Santhosh Kumar K
2026-02-06 19:27       ` Santhosh Kumar K
2026-02-13  8:21       ` Miquel Raynal
2026-02-13  8:21         ` Miquel Raynal
2026-03-17 15:17         ` Miquel Raynal
2026-03-17 15:17           ` Miquel Raynal
2026-03-30 19:56           ` Santhosh Kumar K
2026-03-30 19:56             ` Santhosh Kumar K
2026-01-13 14:16 ` [RFC PATCH v2 12/12] spi: cadence-quadspi: enable PHY for direct reads and writes Santhosh Kumar K
2026-01-13 14:16   ` Santhosh Kumar K
2026-02-05 17:51   ` Miquel Raynal
2026-02-05 17:51     ` Miquel Raynal
2026-02-04 10:29 ` [RFC PATCH v2 00/12] spi: cadence-quadspi: add PHY tuning support Miquel Raynal
2026-02-04 10:29   ` Miquel Raynal
2026-02-05 15:48   ` Miquel Raynal
2026-02-05 15:48     ` Miquel Raynal
2026-02-06 19:28     ` Santhosh Kumar K
2026-02-06 19:28       ` Santhosh Kumar K
2026-02-13  9:01       ` Miquel Raynal
2026-02-13  9:01         ` Miquel Raynal
2026-02-18 18:08         ` Santhosh Kumar K
2026-02-18 18:08           ` Santhosh Kumar K

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h5rvgkjs.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=a-dutta@ti.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mwalle@kernel.org \
    --cc=p-mantena@ti.com \
    --cc=praneeth@ti.com \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=robh@kernel.org \
    --cc=s-k6@ti.com \
    --cc=tudor.ambarus@linaro.org \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.