From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/7] mtd/st_smi: Clear error flags while initiating a fresh write
Date: Thu, 06 Dec 2012 12:39:36 +0100 [thread overview]
Message-ID: <50C083F8.4060408@denx.de> (raw)
In-Reply-To: <acb46f6c779dc8f6c8b1bb2f21a100a1f561e0f0.1354783388.git.vipin.kumar@st.com>
On 12/06/2012 09:47 AM, Vipin Kumar wrote:
> SMI controller reports an error when the code tries to write on the flash area
> with Write Enable command not issued or the bank has come out of the write mode.
>
> This error is reported even with a fresh write once the ERF1 or ERF2 is set.
> Clear these flags while initiating a fresh write
>
> Signed-off-by: Vipin Kumar <vipin.kumar@st.com>
Acked-by: Stefan Roese <sr@denx.de>
Thanks,
Stefan
next prev parent reply other threads:[~2012-12-06 11:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 8:47 [U-Boot] [PATCH v2 0/7] mtd/st_smi: Add fixes for smi driver Vipin Kumar
2012-12-06 8:47 ` [U-Boot] [PATCH v2 1/7] mtd/st_smi: Clear error flags while initiating a fresh write Vipin Kumar
2012-12-06 11:39 ` Stefan Roese [this message]
2012-12-06 8:47 ` [U-Boot] [PATCH v2 2/7] mtd/st_smi: Rearrange the supported devices in alphabetical order Vipin Kumar
2012-12-06 8:47 ` [U-Boot] [PATCH v2 3/7] mtd/st_smi: Add support for Micron N25Q128 Flash Vipin Kumar
2012-12-06 8:47 ` [U-Boot] [PATCH v2 4/7] mtd/st_smi: Avoid issuing multiple WE commands Vipin Kumar
2012-12-06 8:47 ` [U-Boot] [PATCH v2 5/7] mtd/st_smi: Write to flash in a tight loop Vipin Kumar
2012-12-06 11:40 ` Stefan Roese
2012-12-06 8:47 ` [U-Boot] [PATCH v2 6/7] mtd/st_smi: Use page sizes respective to flash Vipin Kumar
2015-12-14 9:15 ` [U-Boot] [U-Boot, v2, " Heiko Schocher
2012-12-06 8:47 ` [U-Boot] [PATCH v2 7/7] mtd/st_smi: Add mtd support for smi Vipin Kumar
2012-12-06 11:41 ` Stefan Roese
2012-12-06 9:05 ` [U-Boot] [PATCH v2 0/7] mtd/st_smi: Add fixes for smi driver Vipin Kumar
2012-12-06 11:42 ` Stefan Roese
2012-12-07 4:43 ` Vipin Kumar
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=50C083F8.4060408@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.