From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Macronix MX25xx MTD SPI flash driver
Date: Mon, 6 Apr 2009 03:39:13 -0400 [thread overview]
Message-ID: <200904060339.14205.vapier@gentoo.org> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E2508402F2@SC-VEXCH1.marvell.com>
On Monday 06 April 2009 03:23:30 Prafulla Wadaskar wrote:
> > > + /* Up to 2 seconds */
> > > + ret = macronix_wait_ready(flash, 2 * CONFIG_SYS_HZ);
> >
> > there's a common flash erase timeout define
>
> Block erase time for Micronix are different than specified in
> spi_flash_internals.h Hence MICRONIX spefic timouts defined and used in
> macronix.c
every flash will have a different erase time, but i have a hard time believing
you picked 2*HZ (2 seconds) because of your part's requirements. more likely
you copied that from the stmicro driver (like every other spi flash driver
until i cleaned them up). the latest tree increases the common timeouts to
seconds rather than milliseconds, so unless your flash is truly truly awful
and requires longer than that, you should use the common define.
> I am ready with the updated patch,
> How should I release it the community?
> 1. new patch with review feedback (with same name)
the current accepted practice is for you to:
- update the patch with all the comments
- add a "v2" to the subject (so it'd be "[PATCH v2] Macronix .....")
- in the comments section of the formatted patch (after the --- marker and
above the diffstat), add notes about what changed in the updated patch
- send it with the reply to header set to the last relevant message in the
patches' thread
> 2. Delta on the top of previous patch
nooooooooo dont ever do this :)
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090406/be05af06/attachment.pgp
next prev parent reply other threads:[~2009-04-06 7:39 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 11:49 [U-Boot] [PATCH] debug_print macros support Prafulla Wadaskar
2009-04-03 11:49 ` [U-Boot] [PATCH] bin_dep.sh Support Prafulla Wadaskar
2009-04-03 11:49 ` [U-Boot] [PATCH] Macronix MX25xx MTD SPI flash driver Prafulla Wadaskar
2009-04-03 14:14 ` Mike Frysinger
2009-04-06 7:23 ` Prafulla Wadaskar
2009-04-06 7:39 ` Mike Frysinger [this message]
2009-04-06 8:27 ` Prafulla Wadaskar
2009-04-06 8:49 ` Mike Frysinger
2009-04-03 17:54 ` [U-Boot] [PATCH] bin_dep.sh Support Wolfgang Denk
2009-04-06 7:34 ` Prafulla Wadaskar
2009-04-06 8:05 ` Wolfgang Denk
2009-04-06 8:13 ` Ronen Shitrit
2009-04-06 8:24 ` Wolfgang Denk
2009-04-06 8:36 ` Ronen Shitrit
2009-04-06 9:11 ` Wolfgang Denk
2009-04-06 9:03 ` Mike Frysinger
2009-04-06 9:16 ` Wolfgang Denk
2009-04-06 9:33 ` Mike Frysinger
2009-04-06 10:28 ` Wolfgang Denk
2009-04-06 10:49 ` Mike Frysinger
2009-04-06 9:38 ` Prafulla Wadaskar
2009-04-06 10:16 ` Mike Frysinger
2009-04-06 11:00 ` Wolfgang Denk
2009-05-26 9:08 ` Stefan Roese
2009-04-06 19:30 ` Scott Wood
2009-04-06 19:49 ` Wolfgang Denk
2009-04-06 23:01 ` Mike Frysinger
2009-04-06 9:39 ` Detlev Zundel
2009-04-06 9:43 ` Prafulla Wadaskar
2009-04-03 17:53 ` [U-Boot] [PATCH] debug_print macros support Wolfgang Denk
2009-04-06 5:32 ` Prafulla Wadaskar
2009-04-06 6:31 ` Mike Frysinger
2009-04-06 6:43 ` Prafulla Wadaskar
2009-04-06 7:56 ` Wolfgang Denk
2009-04-06 8:05 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2009-04-06 15:54 [U-Boot] [PATCH] Macronix MX25xx MTD SPI flash driver Prafulla Wadaskar
2009-04-06 10:46 ` Prafulla Wadaskar
2009-04-06 11:04 ` Mike Frysinger
2009-04-06 11:17 ` Prafulla Wadaskar
2009-04-06 11:11 ` Mike Frysinger
2009-04-06 18:15 ` Wolfgang Denk
2009-04-06 21:48 ` Mike Frysinger
2009-04-06 11:17 ` Mike Frysinger
2009-04-06 18:13 ` Wolfgang Denk
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=200904060339.14205.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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