public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Tokunori Ikegami <ikegami@allied-telesis.co.jp>
Cc: boris.brezillon@free-electrons.com,
	Fabio Bettoni <fbettoni@gmail.com>,
	Chris Packham <chris.packham@alliedtelesis.co.nz>,
	Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH 2/3] mtd: cfi_cmdset_0002: Remove chip_ready() from do_write_buffer()
Date: Fri, 19 Oct 2018 10:31:16 +0200	[thread overview]
Message-ID: <20181019103116.478ff84a@bbrezillon> (raw)
In-Reply-To: <20181019081320.12843-3-ikegami@allied-telesis.co.jp>

On Fri, 19 Oct 2018 17:13:19 +0900
Tokunori Ikegami <ikegami@allied-telesis.co.jp> wrote:

> It is enough to use chip_good() only so chip_ready() is not necessary.
> For this change the order to check timeout is also needed to chagne.

								^ change

And again, you're not explaining why.

> 
> Signed-off-by: Tokunori Ikegami <ikegami@allied-telesis.co.jp>
> Cc: Fabio Bettoni <fbettoni@gmail.com>
> Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>
> Cc: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
> Cc: Boris Brezillon <boris.brezillon@free-electrons.com>
> Cc: linux-mtd@lists.infradead.org
> ---
>  drivers/mtd/chips/cfi_cmdset_0002.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/mtd/chips/cfi_cmdset_0002.c b/drivers/mtd/chips/cfi_cmdset_0002.c
> index 251c9e1675bd..c2e51768a02c 100644
> --- a/drivers/mtd/chips/cfi_cmdset_0002.c
> +++ b/drivers/mtd/chips/cfi_cmdset_0002.c
> @@ -1882,14 +1882,14 @@ static int __xipram do_write_buffer(struct map_info *map, struct flchip *chip,
>  			continue;
>  		}
>  
> -		if (time_after(jiffies, timeo) && !chip_ready(map, adr))
> -			break;
> -
>  		if (chip_good(map, adr, datum)) {
>  			xip_enable(map, chip, adr);
>  			goto op_done;
>  		}
>  
> +		if (time_after(jiffies, timeo))
> +			break;
> +
>  		/* Latency issues. Drop the lock, wait a while and retry */
>  		UDELAY(map, chip, adr, 1);
>  	}

  reply	other threads:[~2018-10-19  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181019081320.12843-1-ikegami@allied-telesis.co.jp>
2018-10-19  8:13 ` [PATCH 1/3] mtd: cfi_cmdset_0002: Change do_write_oneword() to use chip_good() Tokunori Ikegami
2018-10-19  8:29   ` Boris Brezillon
2018-10-19  9:34     ` IKEGAMI Tokunori
2018-10-19  8:13 ` [PATCH 2/3] mtd: cfi_cmdset_0002: Remove chip_ready() from do_write_buffer() Tokunori Ikegami
2018-10-19  8:31   ` Boris Brezillon [this message]
2018-10-19  8:13 ` [PATCH 3/3] mtd: cfi_cmdset_0002: Remove goto statemnet " Tokunori Ikegami
2018-10-19  8:33   ` Boris Brezillon
2018-10-19  9:41     ` IKEGAMI Tokunori
2018-10-19  8:27 ` [PATCH 0/3] mtd: cfi_cmdset_0002: Fix flash write issue for OpenWrt Project Boris Brezillon
     [not found]   ` <CAP7n=KdZ5hdxgZRMixdkuMiVMuCpaXq9hOX_0r1eCQc5Ej4raw@mail.gmail.com>
2018-10-19  9:24     ` IKEGAMI Tokunori

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=20181019103116.478ff84a@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=Joakim.Tjernlund@infinera.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=fbettoni@gmail.com \
    --cc=ikegami@allied-telesis.co.jp \
    --cc=linux-mtd@lists.infradead.org \
    /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