From: Andre Przywara <andre.przywara@arm.com>
To: Yixun Lan <dlan@gentoo.org>, u-boot@lists.denx.de
Cc: linux-sunxi@lists.linux.dev,
Jagan Teki <jagan@amarulasolutions.com>,
Tom Rini <trini@konsulko.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Subject: Re: [PATCH] spi: sunxi: wait for TX/RX fifo reset done
Date: Thu, 30 Apr 2026 11:54:25 +0200 [thread overview]
Message-ID: <e10c1362-59d2-46bf-914f-ef5163336e1f@arm.com> (raw)
In-Reply-To: <20260421-02-spi-fifo-reset-v1-1-e2cdd4bd474d@gentoo.org>
Hi,
On 4/21/26 06:47, Yixun Lan wrote:
> Once reset SPI TX or RX fifo, the underlying hardware need to take
> some time to actually settle down, the two bits will automatically
> clear to 0, so use a poll mechanism to check status bits to make sure
> it's done correctly.
Ah, interesting, thanks for posting this!
I looked into some manuals, and it seems like this self-clearing
property is already used in the A10, so it's fine to use unconditionally.
>
> Signed-off-by: Yixun Lan <dlan@gentoo.org>
Acked-by: Andre Przywara <andre.przywara@arm.com>
If you don't mind, I would pull the below paragraph into the commit
message, since it's useful to have in the git history.
Cheers,
Andre.
P.S. Just curious if we need a similar fix for Linux, or are we saved by
the Linux code spending more time in setup before doing a transfer?
> ---
> On Cubie A7A board which using A733 SoC, we encoutered a SPI nor flash
> timeout issue, it turns out that the SPI fifo reset take a few time to
> settle down, Add a loop to poll the status.
>
> This was the error message shows on A7A board once this issue happened.
>
> => sf probe
> ERROR: sun4i_spi: Timeout transferring data
> Failed to initialize SPI flash at 0:0 (error -2)
> ---
> drivers/spi/spi-sunxi.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/spi/spi-sunxi.c b/drivers/spi/spi-sunxi.c
> index e00532a371b..cf41905c7b7 100644
> --- a/drivers/spi/spi-sunxi.c
> +++ b/drivers/spi/spi-sunxi.c
> @@ -347,7 +347,7 @@ static int sun4i_spi_xfer(struct udevice *dev, unsigned int bitlen,
> struct sun4i_spi_priv *priv = dev_get_priv(bus);
> struct dm_spi_slave_plat *slave_plat = dev_get_parent_plat(dev);
>
> - u32 len = bitlen / 8;
> + u32 rst, val, len = bitlen / 8;
> u8 nbytes;
> int ret;
>
> @@ -363,8 +363,11 @@ static int sun4i_spi_xfer(struct udevice *dev, unsigned int bitlen,
> sun4i_spi_set_cs(bus, slave_plat->cs[0], true);
>
> /* Reset FIFOs */
> - setbits_le32(SPI_REG(priv, SPI_FCR), SPI_BIT(priv, SPI_FCR_RF_RST) |
> - SPI_BIT(priv, SPI_FCR_TF_RST));
> + rst = SPI_BIT(priv, SPI_FCR_RF_RST) | SPI_BIT(priv, SPI_FCR_TF_RST);
> + setbits_le32(SPI_REG(priv, SPI_FCR), rst);
> + ret = readl_poll_timeout(SPI_REG(priv, SPI_FCR), val, !(rst & val), 20);
> + if (ret)
> + return -EBUSY;
>
> while (len) {
> /* Setup the transfer now... */
>
> ---
> base-commit: 88dc2788777babfd6322fa655df549a019aa1e69
> change-id: 20260220-02-spi-fifo-reset-25e371314c3f
>
> Best regards,
next prev parent reply other threads:[~2026-04-30 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 4:47 [PATCH] spi: sunxi: wait for TX/RX fifo reset done Yixun Lan
2026-04-29 16:20 ` Jernej Škrabec
2026-04-30 9:54 ` Andre Przywara [this message]
2026-05-01 12:25 ` Yixun Lan
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=e10c1362-59d2-46bf-914f-ef5163336e1f@arm.com \
--to=andre.przywara@arm.com \
--cc=dlan@gentoo.org \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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