From: Frank Li <Frank.li@nxp.com>
To: Alex Elder <elder@riscstar.com>
Cc: han.xu@nxp.com, broonie@kernel.org, dlan@gentoo.org,
guodong@riscstar.com, linux-spi@vger.kernel.org,
imx@lists.linux.dev, spacemit@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/9] spi: fsl-qspi: allot 1KB per chip
Date: Thu, 23 Oct 2025 19:38:49 -0400 [thread overview]
Message-ID: <aPq8ibj2KzQhtYQT@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20251023175922.528868-7-elder@riscstar.com>
On Thu, Oct 23, 2025 at 12:59:18PM -0500, Alex Elder wrote:
> In fsl_qspi_default_setup(), four registers define the size of blocks of
> data to written to each of four chips that comprise SPI NOR flash storage.
> They are currently defined to be the same as the AHB buffer size (which is
> always 1KB).
>
> The SpacemiT QSPI has an AHB buffer size of 512 bytes, but requires these
> four sizes to be multiples of 1024 bytes.
>
> Define a new field sfa_size in the fsl_qspi_devtype_data structure that, if
> non-zero, will be used instead of the AHB buffer size to define the size of
> these chip regions.
>
> Signed-off-by: Alex Elder <elder@riscstar.com>
> ---
> v2: - New field fsl_qspi_devtype_data->sfa_size now defines the size of
> the serial flash regions if it's non-zero
>
> drivers/spi/spi-fsl-qspi.c | 22 ++++++++++++----------
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/spi/spi-fsl-qspi.c b/drivers/spi/spi-fsl-qspi.c
> index c21e3804cb032..a474d1b341b6a 100644
> --- a/drivers/spi/spi-fsl-qspi.c
> +++ b/drivers/spi/spi-fsl-qspi.c
> @@ -207,6 +207,7 @@ struct fsl_qspi_devtype_data {
> unsigned int txfifo;
> int invalid_mstrid;
> unsigned int ahb_buf_size;
> + unsigned int sfa_size;
> unsigned int quirks;
> bool little_endian;
> };
> @@ -737,6 +738,7 @@ static int fsl_qspi_default_setup(struct fsl_qspi *q)
> {
> void __iomem *base = q->iobase;
> u32 reg, addr_offset = 0;
> + u32 size;
I think use 'sfa_size' is better to read code.
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> int ret;
>
> /* disable and unprepare clock to avoid glitch pass to controller */
> @@ -795,17 +797,17 @@ static int fsl_qspi_default_setup(struct fsl_qspi *q)
> * In HW there can be a maximum of four chips on two buses with
> * two chip selects on each bus. We use four chip selects in SW
> * to differentiate between the four chips.
> - * We use ahb_buf_size for each chip and set SFA1AD, SFA2AD, SFB1AD,
> - * SFB2AD accordingly.
> + *
> + * By default we write the AHB buffer size to each chip, but
> + * a different size can be specified with devtype_data->sfa_size.
> + * The SFA1AD, SFA2AD, SFB1AD, and SFB2AD registers define the
> + * top (end) of these four regions.
> */
> - qspi_writel(q, q->devtype_data->ahb_buf_size + addr_offset,
> - base + QUADSPI_SFA1AD);
> - qspi_writel(q, q->devtype_data->ahb_buf_size * 2 + addr_offset,
> - base + QUADSPI_SFA2AD);
> - qspi_writel(q, q->devtype_data->ahb_buf_size * 3 + addr_offset,
> - base + QUADSPI_SFB1AD);
> - qspi_writel(q, q->devtype_data->ahb_buf_size * 4 + addr_offset,
> - base + QUADSPI_SFB2AD);
> + size = q->devtype_data->sfa_size ? : q->devtype_data->ahb_buf_size;
> + qspi_writel(q, addr_offset + 1 * size, base + QUADSPI_SFA1AD);
> + qspi_writel(q, addr_offset + 2 * size, base + QUADSPI_SFA2AD);
> + qspi_writel(q, addr_offset + 3 * size, base + QUADSPI_SFB1AD);
> + qspi_writel(q, addr_offset + 4 * size, base + QUADSPI_SFB2AD);
>
> q->selected = -1;
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-10-23 23:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 17:59 [PATCH v2 0/9] spi: enable the SpacemiT K1 SoC QSPI Alex Elder
2025-10-23 17:59 ` [PATCH v2 1/9] dt-bindings: spi: fsl-qspi: support SpacemiT K1 Alex Elder
2025-10-23 18:51 ` Conor Dooley
2025-10-23 23:29 ` Frank Li
2025-10-23 17:59 ` [PATCH v2 2/9] dt-bindings: spi: fsl-qspi: add optional resets Alex Elder
2025-10-23 18:52 ` Conor Dooley
2025-10-23 23:32 ` Frank Li
2025-10-24 0:04 ` Alex Elder
2025-10-23 17:59 ` [PATCH v2 3/9] spi: fsl-qspi: add optional reset support Alex Elder
2025-10-23 17:59 ` [PATCH v2 4/9] spi: fsl-qspi: switch predicates to bool Alex Elder
2025-10-23 23:33 ` Frank Li
2025-10-24 0:04 ` Alex Elder
2025-10-23 17:59 ` [PATCH v2 5/9] spi: fsl-qspi: add a clock disable quirk Alex Elder
2025-10-23 23:36 ` Frank Li
2025-10-24 0:04 ` Alex Elder
2025-10-24 2:07 ` Frank Li
2025-10-24 2:31 ` Alex Elder
2025-10-23 17:59 ` [PATCH v2 6/9] spi: fsl-qspi: allot 1KB per chip Alex Elder
2025-10-23 23:38 ` Frank Li [this message]
2025-10-24 0:04 ` Alex Elder
2025-10-23 17:59 ` [PATCH v2 7/9] spi: fsl-qspi: support the SpacemiT K1 SoC Alex Elder
2025-10-23 19:56 ` han.xu
2025-10-24 0:04 ` Alex Elder
2025-10-23 23:41 ` Frank Li
2025-10-24 0:04 ` Alex Elder
2025-10-23 17:59 ` [PATCH v2 8/9] riscv: dts: spacemit: enable K1 SoC QSPI on BPI-F3 Alex Elder
2025-10-23 17:59 ` [PATCH v2 9/9] riscv: defconfig: enable SPI_FSL_QUADSPI as a module Alex Elder
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=aPq8ibj2KzQhtYQT@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=broonie@kernel.org \
--cc=dlan@gentoo.org \
--cc=elder@riscstar.com \
--cc=guodong@riscstar.com \
--cc=han.xu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=spacemit@lists.linux.dev \
/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®