mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Richard Weinberger <richard@nod.at>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 Yogesh S <yogeshs@ti.com>,  Santhosh Kumar K <s-k6@ti.com>,
	 Steam Lin <STLin2@winbond.com>,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/8] Enhance Winbond SPI NAND support
Date: Wed, 30 Jul 2025 11:13:49 +0200	[thread overview]
Message-ID: <87v7nam46q.fsf@bootlin.com> (raw)
In-Reply-To: <20250618-winbond-6-16-rc1-octal-phy-upstream-v1-0-513202126013@bootlin.com> (Miquel Raynal's message of "Wed, 18 Jun 2025 14:14:17 +0200")

Hello,

On 18/06/2025 at 14:14:17 +02, Miquel Raynal <miquel.raynal@bootlin.com> wrote:

> Both w25n**jw and w35n**jw chips have a "normal" and a "high speed"
> mode. In order to use the high speed modes, we need to configure
> internal registers and adapt the number of dummy cycles. The benefits
> are too interesting for not paying attention to this little extra
> configuration. In particular, it is an important building block for the
> introduction of PHY calibration on TI SPI controllers. With these
> changes combined, the frequency used on these chips can be bumped from
> ~25MHz up to 166MHz.
>
> This series was tested on TI AM62A SK with a W35N01JW and on Nuvoton
> MA35D with a W25N01JW. At low speeds, this series does not bring any
> improvement. However when enabling high speed modes (on TI's platform),
> the difference is outstanding:
>
> W35N*JW running in 1S-8S-8S @ 25MHz:
>
> 	 eraseblock read speed is 9552 KiB/s
> 	 page read speed is 9516 KiB/s
> 	 2 page read speed is 9552 KiB/s
>
> W35N*JW running in 1S-8S-8S @ 166MHz:
>
> 	eraseblock read speed is 35555 KiB/s
> 	page read speed is 33684 KiB/s
> 	2 page read speed is 35068 KiB/s
>
> Enabling high speeds currently requires applying extra patches from TI
> to enable PHY calibration. They are currently in the upstreaming process.
>
> Link: https://github.com/miquelraynal/linux/tree/winbond/6.16-rc1/octal-phy
>
> In order to introduce all these variants and derive the quickest one, I
> had to improve a bit the helper deriving the time an ops would
> take. These changes can go through the spi tree, the other patches do
> not depend on them and the performance hit is rather acceptable without.
>
> While at adding maximum operation frequencies, I realized I got myself
> confused with the macro parameters due to some of them being
> optional (with variable arguments in macros). I decided it was too error
> prone so I propose to add these values on all READ_FROM_CACHE
> variants (where they are often relevant).
>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
> Miquel Raynal (8):
>       spi: spi-mem: Use picoseconds for calculating the op durations
>       spi: spi-mem: Take into account the actual maximum frequency
>       mtd: spinand: Fix macro alignment
>       mtd: spinand: Add a frequency field to all READ_FROM_CACHE variants
>       mtd: spinand: Add a ->configure_chip() hook
>       mtd: spinand: winbond: Enable high-speed modes on w25n0xjw
>       mtd: spinand: winbond: Enable high-speed modes on w35n0xjw
>       mtd: spinand: winbond: Add comment about the maximum frequency

Series applied to nand/next after fixing conflicts due to some fixes.

Thanks,
Miquèl

      parent reply	other threads:[~2025-07-30  9:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 12:14 Miquel Raynal
2025-06-18 12:14 ` [PATCH 1/8] spi: spi-mem: Use picoseconds for calculating the op durations Miquel Raynal
2025-06-18 12:24   ` Mark Brown
2025-06-18 12:14 ` [PATCH 2/8] spi: spi-mem: Take into account the actual maximum frequency Miquel Raynal
2025-06-18 12:30   ` Mark Brown
2025-06-18 12:14 ` [PATCH 3/8] mtd: spinand: Fix macro alignment Miquel Raynal
2025-06-18 12:14 ` [PATCH 4/8] mtd: spinand: Add a frequency field to all READ_FROM_CACHE variants Miquel Raynal
2025-06-18 12:14 ` [PATCH 5/8] mtd: spinand: Add a ->configure_chip() hook Miquel Raynal
2025-06-18 12:14 ` [PATCH 6/8] mtd: spinand: winbond: Enable high-speed modes on w25n0xjw Miquel Raynal
2025-06-18 12:14 ` [PATCH 7/8] mtd: spinand: winbond: Enable high-speed modes on w35n0xjw Miquel Raynal
2025-06-18 12:14 ` [PATCH 8/8] mtd: spinand: winbond: Add comment about the maximum frequency Miquel Raynal
2025-07-30  9:13 ` Miquel Raynal [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=87v7nam46q.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=STLin2@winbond.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=s-k6@ti.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vigneshr@ti.com \
    --cc=yogeshs@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

all inboxes | Powered by JetHome®