From: Marek Vasut <marex@denx.de>
To: linux-mtd@lists.infradead.org
Cc: Jeremy Garff <jer@jers.net>
Subject: Re: [PATCH] spi-nor: Fix for Freescale i.MX6 reboot issue when using a N25Q00A boot device.
Date: Thu, 25 Sep 2014 19:09:41 +0200 [thread overview]
Message-ID: <201409251909.41740.marex@denx.de> (raw)
In-Reply-To: <CAKbvp-NuFWzCCT+eo-WO47kazNuHbcA4KxhjDLYGR9p9Jh9FRg@mail.gmail.com>
On Saturday, August 16, 2014 at 08:14:05 PM, Jeremy Garff wrote:
> This is my first submission to the linux-mtd list. I found
Found yes
> and fixed
Fixed no ;-)
> a issue related to the i.MX6 when using a N25Q00A spi-nor as the boot
> device. The following is a patch and more detailed description. As
> this is my first submission to this list, so please let me know you
> have any questions or concerns.
Well, the problem is that the SPI NOR ends in undefined state when you reset the
board. The problem is not in Linux, the problem is in your board. You should use
the RESET-OUTPUT pin of your MX6 to implement proper reset sequencing for the
SPI NOR.
This patch would not work in case you were doing a PageProgram operation and I
came around and mashed the 'reset' button on your board. The SPI NOR would be
somewhere in the middle of the PP and your MX6 would simply not boot.
So the solution here is to fix your hardware ;-)
btw this is a common issue, we should really document this before more people
get hurt.
btw2 Spansion does much better job, their SPI NORs have RESET pin, so you don't
need to implement logic to power cycle the SPI NOR.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-09-25 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 18:14 [PATCH] spi-nor: Fix for Freescale i.MX6 reboot issue when using a N25Q00A boot device Jeremy Garff
2014-09-25 17:09 ` Marek Vasut [this message]
2014-09-26 19:46 ` Jeremy Garff
2014-09-26 23:42 ` Marek Vasut
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=201409251909.41740.marex@denx.de \
--to=marex@denx.de \
--cc=jer@jers.net \
--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 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.