mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>
Subject: Re: [RFC] spi-nor: Use different timeout values for write and erase operations
Date: Sat, 6 Feb 2016 19:19:04 -0800	[thread overview]
Message-ID: <CAHQ1cqEJmDM+ZG-Pv6mnZnSHVr0_SDbdFaCVbXtyvVpGRq9KSg@mail.gmail.com> (raw)
In-Reply-To: <1454790180-3156-1-git-send-email-andrew.smirnov@gmail.com>

On Sat, Feb 6, 2016 at 12:23 PM, Andrey Smirnov
<andrew.smirnov@gmail.com> wrote:
> Some chips take longer than 40 seconds to perform certain
> operations. One concrete example would be M25P128 that, according to
> its spec, can take up to 250 seconds to perform a chip erase.
>
> This commit:
>
>      - Adds 'wait_time` parameter to spi_nor_wait_till_ready() so that
>        each individual caller of would be able to use custom timeout
>
>      - Adds timings information to flash_info and nor_spi structures
>        to specify sector and chip erase timeouts
>
>      - Modifies the code of spi_nor_erase() to make use of previously
>        mentioned changes
>
> Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>


I was pointed to a kernel patch that solves the same problem in a less
verbose way:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=09b6a377687b885565339e60bc62566433a0406f

so instead of going with what's in my RFC I think I'll port those
kernel changes to Barebox.

Sorry for the noise.

Andrey

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2016-02-07  3:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06 20:23 Andrey Smirnov
2016-02-07  3:19 ` Andrey Smirnov [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=CAHQ1cqEJmDM+ZG-Pv6mnZnSHVr0_SDbdFaCVbXtyvVpGRq9KSg@mail.gmail.com \
    --to=andrew.smirnov@gmail.com \
    --cc=barebox@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