From: Santhosh Kumar K <s-k6@ti.com>
To: Michal Simek <michal.simek@amd.com>,
"Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"pratyush@kernel.org" <pratyush@kernel.org>,
"mwalle@kernel.org" <mwalle@kernel.org>,
"takahiro.kuwano@infineon.com" <takahiro.kuwano@infineon.com>
Cc: "linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"praneeth@ti.com" <praneeth@ti.com>,
"u-kumar1@ti.com" <u-kumar1@ti.com>,
"a-dutta@ti.com" <a-dutta@ti.com>,
"git (AMD-Xilinx)" <git@amd.com>,
"Amit Mohapatra" <amitrkcian2002@gmail.com>, <s-k6@ti.com>
Subject: Re: [PATCH v4 00/16] spi: cadence-quadspi: add PHY tuning support
Date: Sat, 18 Jul 2026 00:30:29 +0530 [thread overview]
Message-ID: <9318b1a8-eed7-4d27-94ca-5137269f8ecf@ti.com> (raw)
In-Reply-To: <979c6ed6-4e75-416a-ae5f-a2a8d3ec1a4c@amd.com>
Hello Michal,
On 16/07/26 19:27, Michal Simek wrote:
>
>
> On 7/16/26 08:04, Santhosh Kumar K wrote:
>> Hello Amit,
>>
>> Apologies for the delayed response.
>>
>> On 22/06/26 10:00, Mahapatra, Amit Kumar wrote:
>>> AMD General
>>>
>>> Hello Santosh,
>>>
>>>> -----Original Message-----
>>>> From: Santhosh Kumar K <s-k6@ti.com>
>>>> Sent: Thursday, June 18, 2026 1:07 PM
>>>> To: broonie@kernel.org; robh@kernel.org; krzk+dt@kernel.org;
>>>> conor+dt@kernel.org; miquel.raynal@bootlin.com; richard@nod.at;
>>>> vigneshr@ti.com; pratyush@kernel.org; mwalle@kernel.org;
>>>> takahiro.kuwano@infineon.com
>>>> Cc: 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: [PATCH v4 00/16] spi: cadence-quadspi: add PHY tuning support
>>>>
>>>> This series implements PHY tuning support for the Cadence QSPI
>>>> controller to
>>>> enable reliable high-speed operations. Without PHY tuning,
>>>> controllers use
>>>> conservative timing that limits performance. PHY tuning calibrates
>>>> RX/TX delay lines
>>>> to find optimal data capture timing windows, enabling operation up
>>>> to the controller's
>>>> maximum frequency.
>>>>
>>>> Background:
>>>> High-speed SPI memory controllers require precise timing calibration
>>>> for reliable
>>>> operation. At higher frequencies, board-to-board variations make
>>>> fixed timing
>>>> parameters inadequate. The Cadence QSPI controller includes a PHY
>>>> interface with
>>>> programmable delay lines (0-127 taps) for RX and TX paths, but these
>>>> require
>>>> runtime calibration to find the valid timing window.
>>>>
>>>> Approach:
>>>> Add SDR/DDR PHY tuning algorithms for the Cadence controller:
>>>>
>>>> SDR Mode Tuning (1D search):
>>>> - Searches for two consecutive valid RX delay windows
>>>> - Selects the larger window and uses its midpoint for maximum margin
>>>> - TX delay fixed at maximum (127) as it's less critical in SDR
>>>>
>>>> DDR Mode Tuning (2D search):
>>>> - Finds RX boundaries (rxlow/rxhigh) using TX window sweeps
>>>> - Finds TX boundaries (txlow/txhigh) at fixed RX positions
>>>> - Defines valid region corners and detects gaps via binary search
>>>> - Applies temperature compensation for optimal point selection
>>>> - Handles single or dual passing regions with different strategies
>>>
>>> Thank you for this series. I had a question regarding the Virtual Concat
>>> driver patch series [1]. Now that it has been merged into the kernel and
>>> enables support for multiple flash devices connected in stacked mode-
>>> where
>>> each flash device is probed and configured independently-if both flash
>>> parts are required to operate in DDR mode, each device would need to
>>> perform tuning and store its tuning data separately.
>>>
>>> Given this, should we consider this use case and adapt the tuning
>>> architecture to support it?
>>>
>>> I'd appreciate your thoughts on this.
>>
>> Good point.
>>
>> The current implementation already stores the calibration state per
>> chip select (delay line settings, tuned flags, and operation templates),
>> so the data model supports independent tuning for each device.
>>
>> However, the runtime path that enables PHY mode does not restore the
>> per-CS delay line settings when switching between chip selects. As a
>> result, consecutive PHY accesses to different devices could end up using
>> the wrong delay line settings.
>>
>> This can be addressed with a small change by reading the currently
>> programmed DLL and reprogramming the PHY configuration registers
>> whenever they differ from the calibrated values for the selected chip.
>
> Are you going to include it to your series?
Yes, I've added support for this in the v5 series, which I just
posted. [0]
[0] https://lore.kernel.org/linux-spi/20260717185116.2065505-1-s-k6@ti.com/
Thanks,
Santhosh.
>
> Thanks,
> Michal
prev parent reply other threads:[~2026-07-17 19:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 7:37 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-22 9:17 ` Krzysztof Kozlowski
2026-06-22 17:11 ` Miquel Raynal
2026-07-16 5:54 ` Santhosh Kumar K
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-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-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:37 ` [PATCH v4 06/16] spi: cadence-quadspi: move cqspi_readdata_capture earlier Santhosh Kumar K
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-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-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:37 ` [PATCH v4 11/16] spi: cadence-quadspi: enable PHY for direct reads Santhosh Kumar K
2026-06-18 7:37 ` [PATCH v4 12/16] spi: cadence-quadspi: enable PHY for indirect writes Santhosh Kumar K
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-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-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
2026-07-17 19:00 ` Santhosh Kumar K [this message]
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=9318b1a8-eed7-4d27-94ca-5137269f8ecf@ti.com \
--to=s-k6@ti.com \
--cc=a-dutta@ti.com \
--cc=amit.kumar-mahapatra@amd.com \
--cc=amitrkcian2002@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=michal.simek@amd.com \
--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