From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spi: designware_spi: Fix off-by-one for checking fifo depth
Date: Fri, 19 Dec 2014 08:35:34 +0100 [thread overview]
Message-ID: <5493D546.1080300@denx.de> (raw)
In-Reply-To: <1418964032.32166.1.camel@phoenix>
Hi Axel,
On 19.12.2014 05:40, Axel Lin wrote:
> The depth could be from 2 to 256 from HW spec, so fix off-by-one for checking
> fifo depth.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> Hi,
> I don't have this hardware handy, so please test it.
> drivers/spi/designware_spi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/spi/designware_spi.c b/drivers/spi/designware_spi.c
> index 98c9f03..14d0c23 100644
> --- a/drivers/spi/designware_spi.c
> +++ b/drivers/spi/designware_spi.c
> @@ -164,7 +164,7 @@ static void spi_hw_init(struct dw_spi_priv *priv)
> if (!priv->fifo_len) {
> u32 fifo;
>
> - for (fifo = 2; fifo <= 257; fifo++) {
> + for (fifo = 2; fifo <= 256; fifo++) {
> dw_writew(priv, DW_SPI_TXFLTR, fifo);
> if (fifo != dw_readw(priv, DW_SPI_TXFLTR))
> break;
Please note that this code was not written by myself but is based on the
Linux kernel version. And from my current understanding, this code tries
to detect the FIFO size. So this 257 being bigger than the max value of
256 is most likely correct. Also another 257 is a few lines below your code:
dws->fifo_len = (fifo == 257) ? 0 : fifo;
So I don't think that we need to change this here.
BTW: It might be better to send this patch (or a question about this 256
vs 257) to the SPI Linux mailing list. The maintainer there will have
deeper knowledge about this issue.
Thanks,
Stefan
next prev parent reply other threads:[~2014-12-19 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 4:40 [U-Boot] [PATCH] spi: designware_spi: Fix off-by-one for checking fifo depth Axel Lin
2014-12-19 7:35 ` Stefan Roese [this message]
2014-12-19 7:44 ` Axel Lin
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=5493D546.1080300@denx.de \
--to=sr@denx.de \
--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