Devicetree
 help / color / mirror / Atom feed
From: Santhosh Kumar K <s-k6@ti.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	Krzysztof Kozlowski <krzk@kernel.org>
Cc: <broonie@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <richard@nod.at>, <vigneshr@ti.com>,
	<pratyush@kernel.org>, <mwalle@kernel.org>,
	<takahiro.kuwano@infineon.com>, <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>, <a-dutta@ti.com>, <s-k6@ti.com>
Subject: Re: [PATCH v4 02/16] spi: dt-bindings: add spi-phy-pattern-partition property
Date: Thu, 16 Jul 2026 11:24:15 +0530	[thread overview]
Message-ID: <45821dff-720b-43ac-899e-03f200d48b9d@ti.com> (raw)
In-Reply-To: <87zf0m5wlx.fsf@bootlin.com>

Hello Krzysztof and Miquel,

Apologies for the delayed response.

On 22/06/26 22:41, Miquel Raynal wrote:
> Hello,
> 
>>> +  spi-phy-pattern-partition:
>>
>> Is this specific to SPI-based MTD/NAND or rather broader - specific to
>> MTD/NAND memories, regardless of interface? Feels like the second, thus
>> maybe should be placed into the NAND bindings.
>>
>> If the first, then in below description:
>>
>> s/PHY/SPI PHY/ to be clear that this is about SPI, not the memory
>> itself.
> 
> As far as I know, there is no raw NAND controller with such
> capability. In the raw/parallel NAND world, timings are well defined by
> the ONFI specification, it covers both the bus timings and the minimal
> requirements for the chips. There is a method to query what "timing mode"
> the NAND chip supports, and then we tune the controller registers to fit
> the highest supported timings (capped by possible controller limits).
> 
> In the SPI world it is different. No specific timing has ever been
> globally defined, so every manufacturer has its own capabilities which
> are not discoverable dynamically. The routing also weights a lot. I
> would say that we can safely keep this property SPI related, because it
> is about the SPI bus being used with optimized timings, rather than some
> kind of memory specific feature.
> 
> The reason why we need a property in those memories for the feature to
> work, is because we need to make data transfers with a known pattern,
> thus requiring to read the pattern from the internal array somehow.
> 
> Therefore, we shall indeed go for the s/PHY/SPI PHY/ naming indeed.

Agreed, will replace 'PHY' with 'SPI PHY' in the description.

Thanks,
Santhosh.

> 
> Thanks,
> Miquèl


  reply	other threads:[~2026-07-16  5:55 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18  7:37 [PATCH v4 00/16] spi: cadence-quadspi: add PHY tuning support Santhosh Kumar K
2026-06-18  7:37 ` [PATCH v4 01/16] spi: dt-bindings: add spi-max-post-config-frequency property Santhosh Kumar K
2026-06-18 16:36   ` Conor Dooley
2026-06-22  9:14   ` Krzysztof Kozlowski
2026-06-22 19:46     ` Conor Dooley
2026-06-29 15:41     ` Miquel Raynal
2026-07-16  5:52       ` Santhosh Kumar K
2026-06-18  7:37 ` [PATCH v4 02/16] spi: dt-bindings: add spi-phy-pattern-partition property Santhosh Kumar K
2026-06-18  7:50   ` sashiko-bot
2026-06-22  9:17   ` Krzysztof Kozlowski
2026-06-22 17:11     ` Miquel Raynal
2026-07-16  5:54       ` Santhosh Kumar K [this message]
2026-06-18  7:37 ` [PATCH v4 03/16] spi: parse spi-max-post-config-frequency into post_config_max_speed_hz Santhosh Kumar K
2026-06-18  7:54   ` sashiko-bot
2026-06-29 15:43   ` Miquel Raynal
2026-06-18  7:37 ` [PATCH v4 04/16] spi: spi-mem: teach spi_mem_adjust_op_freq() about post-config ops Santhosh Kumar K
2026-06-18  8:02   ` sashiko-bot
2026-07-02 13:32   ` Miquel Raynal
2026-06-18  7:37 ` [PATCH v4 05/16] spi: spi-mem: add execute_tuning callback and spi_mem_execute_tuning() Santhosh Kumar K
2026-06-18  7:57   ` sashiko-bot
2026-06-18  7:37 ` [PATCH v4 06/16] spi: cadence-quadspi: move cqspi_readdata_capture earlier Santhosh Kumar K
2026-06-18  7:48   ` sashiko-bot
2026-06-18  7:37 ` [PATCH v4 07/16] spi: cadence-quadspi: add DQS support to read data capture Santhosh Kumar K
2026-06-18  7:37 ` [PATCH v4 08/16] spi: cadence-quadspi: add PHY tuning support Santhosh Kumar K
2026-06-18  7:59   ` sashiko-bot
2026-06-19 17:33   ` Mark Brown
2026-07-16  5:56     ` Santhosh Kumar K
2026-06-18  7:37 ` [PATCH v4 09/16] spi: cadence-quadspi: skip DDR PHY tuning for 2-byte-address ops (i2383) Santhosh Kumar K
2026-06-18  8:04   ` sashiko-bot
2026-07-02 13:35   ` Miquel Raynal
2026-07-16  5:58     ` Santhosh Kumar K
2026-06-18  7:37 ` [PATCH v4 10/16] spi: cadence-quadspi: refactor direct read path for PHY support Santhosh Kumar K
2026-06-18  7:57   ` sashiko-bot
2026-06-18  7:37 ` [PATCH v4 11/16] spi: cadence-quadspi: enable PHY for direct reads Santhosh Kumar K
2026-06-18  7:53   ` sashiko-bot
2026-06-18  7:37 ` [PATCH v4 12/16] spi: cadence-quadspi: enable PHY for indirect writes Santhosh Kumar K
2026-06-18  7:53   ` sashiko-bot
2026-06-18  7:37 ` [PATCH v4 13/16] mtd: spinand: extract variant ranking logic into spinand_op_find_best() Santhosh Kumar K
2026-07-02 13:41   ` Miquel Raynal
2026-07-16  6:00     ` Santhosh Kumar K
2026-06-18  7:37 ` [PATCH v4 14/16] mtd: spinand: negotiate optimal PHY operating point before dirmap creation Santhosh Kumar K
2026-06-18  8:02   ` sashiko-bot
2026-07-02 15:08   ` Miquel Raynal
2026-07-16  6:02     ` Santhosh Kumar K
2026-06-18  7:37 ` [PATCH v4 15/16] mtd: spi-nor: extract read op template construction into helper Santhosh Kumar K
2026-06-18  7:37 ` [PATCH v4 16/16] mtd: spi-nor: run PHY tuning after init and update dirmap frequency Santhosh Kumar K
2026-06-18  8:01   ` sashiko-bot
2026-06-22  4:30 ` [PATCH v4 00/16] spi: cadence-quadspi: add PHY tuning support Mahapatra, Amit Kumar
2026-07-16  6:04   ` Santhosh Kumar K
2026-07-16 13:57     ` Michal Simek

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=45821dff-720b-43ac-899e-03f200d48b9d@ti.com \
    --to=s-k6@ti.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=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=mwalle@kernel.org \
    --cc=praneeth@ti.com \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=robh@kernel.org \
    --cc=takahiro.kuwano@infineon.com \
    --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