From: Thomas Chou <thomas@wytron.com.tw>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] altera_qspi: fix erase and write error code
Date: Sun, 6 Dec 2015 11:33:08 +0800 [thread overview]
Message-ID: <5663AC74.50501@wytron.com.tw> (raw)
In-Reply-To: <1448960876-22615-2-git-send-email-thomas@wytron.com.tw>
On 2015?12?01? 17:07, Thomas Chou wrote:
> Fix erase and write error code, which should be "protected".
>
>>From the "Embedded Peripherals IP User Guide" of Altera,
>
> The "Illegal write" flag indicates that a write instruction is
> targeting a protected sector on the flash memory. This bit is
> set to indicate that the IP has cancelled a write instruction.
>
> The "Illegal erase" flag indicates that an erase instruction has
> been set to a protected sector on the flash memory. This bit is
> set to indicate that the IP has cancelled the erase instruction.
>
> Signed-off-by: Thomas Chou <thomas@wytron.com.tw>
> ---
> v2
> add description as suggested by Marek.
>
> drivers/mtd/altera_qspi.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Applied to u-boot-nios.
next prev parent reply other threads:[~2015-12-06 3:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 11:38 [U-Boot] [PATCH 1/2] altera_qspi: add lock unlock ops Thomas Chou
2015-11-29 11:38 ` [U-Boot] [PATCH 2/2] altera_qspi: fix erase and write error code Thomas Chou
2015-11-29 13:35 ` Marek Vasut
2015-12-01 7:21 ` Chin Liang See
2015-11-29 13:34 ` [U-Boot] [PATCH 1/2] altera_qspi: add lock unlock ops Marek Vasut
2015-12-01 7:09 ` Chin Liang See
2015-12-01 9:07 ` [U-Boot] [PATCH v2 " Thomas Chou
2015-12-01 9:07 ` [U-Boot] [PATCH v2 2/2] altera_qspi: fix erase and write error code Thomas Chou
2015-12-01 13:24 ` Marek Vasut
2015-12-06 3:33 ` Thomas Chou [this message]
2015-12-01 13:23 ` [U-Boot] [PATCH v2 1/2] altera_qspi: add lock unlock ops Marek Vasut
2015-12-06 3:32 ` Thomas Chou
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=5663AC74.50501@wytron.com.tw \
--to=thomas@wytron.com.tw \
--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