public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Michael Walle" <mwalle@kernel.org>
Cc: "Santhosh Kumar K" <s-k6@ti.com>,  <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>,  <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: Fri, 20 Feb 2026 09:21:32 +0100	[thread overview]
Message-ID: <87h5rbsu43.fsf@bootlin.com> (raw)
In-Reply-To: <DGIXI3RVPSJW.3J77RFU4JK6O2@kernel.org> (Michael Walle's message of "Thu, 19 Feb 2026 13:14:39 +0100")

On 19/02/2026 at 13:14:39 +01, "Michael Walle" <mwalle@kernel.org> wrote:

> On Thu Feb 5, 2026 at 6:35 PM CET, Miquel Raynal wrote:
>> 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.
>
> Usually, a DQS pin is optional. AFAIK, there is no requirement for
> it. I.e. it will probably work fine with slower frequencies and
> using an internal loopback. So if you run your flash with slower
> frequency you can probably save one pin and use it for something
> different.
>
> What I wanted to say is, that not having a DQS pin wired is not
> really a mistake. But "dqs-not-wired" sounds exactly like it.
> So IMHO it should be the other way around and the device tree should
> tell you that *is* wired, if we cannot find detect it otherwise,
> like looking at pinmuxing for example (not sure that is feasible
> though).

I was in favour of the opt-out property because I feel like it doesn't
make sense to fill in the high speed spi property which involves tuning,
without wiring the DQS pin. It is possible, but if you're looking for
speed, it doesn't make much sense IMO. Hence I was seeing this as a
specific case which legitimately needs a property. But I don't want to
bikeshed on that for too long, I'm fine with the opposite approach,
let's make it a "dqs-is-wired" (or something alike) property.

Thanks,
Miquèl

  reply	other threads:[~2026-02-20  8:21 UTC|newest]

Thread overview: 46+ 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 ` [RFC PATCH v2 01/12] spi: dt-bindings: add spi-has-dqs property Santhosh Kumar K
2026-02-04 10:46   ` Miquel Raynal
2026-02-05 17:46     ` Santhosh Kumar K
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 ` [RFC PATCH v2 03/12] mtd: spinand: perform controller tuning during probe Santhosh Kumar K
2026-02-05 17:35   ` Miquel Raynal
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 ` [RFC PATCH v2 05/12] mtd: spi-nor: perform controller tuning during probe 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-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-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-02-05 17:35   ` Miquel Raynal
2026-02-19 12:14     ` Michael Walle
2026-02-20  8:21       ` Miquel Raynal [this message]
2026-01-13 14:16 ` [RFC PATCH v2 09/12] spi: cadence-quadspi: add PHY tuning infrastructure Santhosh Kumar K
2026-02-05 17:39   ` Miquel Raynal
2026-02-06 19:25     ` Santhosh Kumar K
2026-02-13  8:18       ` Miquel Raynal
2026-02-18 18:07         ` Santhosh Kumar K
2026-02-19 10:30           ` Miquel Raynal
2026-02-09  9:48   ` Michael Walle
2026-02-12 10:50     ` Miquel Raynal
2026-02-12 11:14       ` Michael Walle
2026-02-12 12:55         ` Miquel Raynal
2026-02-18 18:07           ` Santhosh Kumar K
2026-02-19  8:33             ` Michael Walle
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-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-02-05 17:47   ` Miquel Raynal
2026-02-06 19:27     ` Santhosh Kumar K
2026-02-13  8:21       ` Miquel Raynal
2026-03-17 15:17         ` Miquel Raynal
2026-01-13 14:16 ` [RFC PATCH v2 12/12] spi: cadence-quadspi: enable PHY for direct reads and writes Santhosh Kumar K
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-05 15:48   ` Miquel Raynal
2026-02-06 19:28     ` Santhosh Kumar K
2026-02-13  9:01       ` Miquel Raynal
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=87h5rbsu43.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox